xmr-btc-swap/CHANGELOG.md

# Changelog

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

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]

### Added

- A changelog file.

### Fixed

- Make monero_wallet_rpc readiness check language agnostic. The readiness check was
  failing on non-english language systems preventing users from starting the swap-cli
  and asb.

### 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.

[Unreleased]: https://github.com/comit-network/xmr-btc-swap/compare/v0.3...HEAD
Add CHANGELOG file 3 years ago			`# Changelog`

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

			`The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),`
			`and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).`

			`## [Unreleased]`

			`### Added`

			`- A changelog file.`

Use language agnostic heuristic to check if monero_wallet_rpc is ready Our strategy of searching for a english string to determine if monero_wallet_rpc is ready is not compatible with languages other than english. Instead we assume the monero rpc is ready if it has stopped writing to stdout. We make a json rpc request to confirm this. A better solution would have been to configure the monero_wallet_rpc to always output in english but there is not command line argument to configure the language. Closes #353. 3 years ago			`### Fixed`

			`- Make monero_wallet_rpc readiness check language agnostic. The readiness check was`
			`failing on non-english language systems preventing users from starting the swap-cli`
			`and asb.`

Alice to validate Bob's PSBT for correctness In order for the re-construction of TxLock to be meaningful, we limit `Message2` to the PSBT instead of the full struct. This is a breaking change in the network layer. The PSBT is valid if: - It has at most two outputs (we allow a change output) - One of the outputs pays the agreed upon amount to a shared output script Resolves #260. 3 years ago			`### 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.`

Add CHANGELOG file 3 years ago			`[Unreleased]: https://github.com/comit-network/xmr-btc-swap/compare/v0.3...HEAD`