Git-Mirrors/xmr-btc-swap
1
0
Fork 0
mirror of https://github.com/comit-network/xmr-btc-swap.git synced 2024-12-24 23:19:34 -05:00
Code Issues Packages Projects Releases Wiki Activity
7c18ae23a8
xmr-btc-swap/CHANGELOG.md
Daniel Karzel 69f7565746
!fixup Different default directories for CLI and ASB 
Using the same default directory as data-/config-dir has caused unwanted side effects when running both applications on the same machine.
Use these directory names:
- ASB: xmr-btc-swap/asb
- CLI: xmr-btc-swap/cli

Since the functionality is now application specific the respective functions were moved into the appropriate module of the application.
2021-04-30 11:03:13 +10:00

4.1 KiB
Raw Blame History

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Unreleased

Fixed

  • An issue where both the ASB and the CLI point to the same default directory xmr-btc-swap for storing data. The asb now uses xmr-btc-swap/asb and the CLI xmr-btc-swap/cli as default directory. This is a breaking change. If you want to access data created by a previous version you will have to rename the data folder or one of the following:
    1. For the CLI you can use --data-dir to point to the old directory.
    2. For the ASB you can change the data-dir in the config file of the ASB.

0.5.0 - 2021-04-17

Changed

  • The quote protocol returns JSON encoded data instead of CBOR. This is a breaking change in the protocol handling, old CLI versions will not be able to process quote requests of ASBs running this version.

Fixed

  • An issue where concurrent swaps with the same peer would cause the ASB to handle network communication incorrectly. To fix this, all messages are now tagged with a unique identifier that is agreed upon at the start of the swap. This is a breaking change in the network layer and hence old versions are not compatible with this version. We advise to also not resume any swaps that have been created with an older version. It is recommended to reset / delete the database after upgrading.
  • An issue where the CLI would not reconnect to the ASB in case the network connection dropped. We now attempt to re-establish the connection using an exponential backoff but will give up eventually after 5 minutes.

Added

  • Websocket support for the ASB. The ASB is now capable to listen on both TCP and Websocket connections. Default websocket listening port is 9940.
  • Tor support as an optional feature. If ASB detects that Tor's control port is open, a hidden service is created for the network it is listening on (currently 2). The Tor control port as well as Tor socks5 proxy port is configurable.

0.4.0 - 2021-04-06

Changed

  • The resume command of the swap CLI no longer require the --seller-peer-id parameter. This information is now saved in the database.

Added

  • A changelog file.
  • Automatic resume of unfinished swaps for the asb upon startup. Unfinished swaps from earlier versions will be skipped.
  • A configurable spread for the ASB that is applied to the asking price received from the Kraken price ticker. The default value is 2% and can be configured using the --ask-spread parameter. See ./asb --help for details.

Changed

  • Require the buyer to specify the connection details of the peer they wish to swap with. Throughout the public demo phase of this project, the CLI traded with us by default if the peer id and multiaddress of the seller were not specified. Having the defaults made it easy for us to give something to the community that can easily be tested, however it is not aligned with our long-term vision of a decentralised network of sellers. We have removed these defaults forcing the user to specify the seller they wish to trade with.

Fixed

  • An issue where the swap CLI would fail on systems that were set to a locale different than English. A bad readiness check when waiting for monero-wallet-rpc to be ready caused the CLI to hang forever, preventing users from perform a swap.

Security

  • Fixed an issue where Alice would not verify if Bob's Bitcoin lock transaction is semantically correct, i.e. pays the agreed upon amount to an output owned by both of them. Fixing this required a breaking change on the network layer and hence old versions are not compatible with this version.