4344554730
894: Reduce `bitcoin_finality_confirmations` from 2 to 1 r=binarybaron a=binarybaron Reduces `bitcoin_finality_confirmations` from 2 to 1. This lowers the total time needed for a swap by an average of 10 minutes I'm aware that this has been proposed before (https://github.com/comit-network/xmr-btc-swap/pull/800) and was rejected. > On the ASB, the bitcoin finality confirmations can be set to 1 using the config file. This will get you the swap reduction time you desire. I believe this is not correct. There is no way for ASB operators to configure the `bitcoin_finality_confirmations` setting. Only the `target_block` can be configured manually, but this is only used for estimating the fee rate when a btc transaction is published and not for deciding when it is safe to assume that the transaction is finalized. E.g the `config.toml` file of my (testate) asb ``` [data] dir = "/root/.local/share/xmr-btc-swap/asb/testnet" [network] listen = ["/ip4/0.0.0.0/tcp/9939", "/ip4/0.0.0.0/tcp/9940/ws"] external_addresses = ["/dnsaddr/unstoppableswap.net"] rendezvous_point = "/dnsaddr/discover.unstoppableswap.net/p2p/12D3KooWA6cnqJpVnreBVnoro8midDL9Lpzmg8oJPoAGi7YYaamE" [bitcoin] electrum_rpc_url = "ssl://electrum.blockstream.info:60002" target_block = 1 # My asb still waits for 2 confirmations on the btc lock tx network = "Testnet" [monero] wallet_rpc_url = "http://127.0.0.1:38083/json_rpc" network = "Stagenet" [tor] control_port = 9051 socks5_port = 9050 [maker] min_buy_btc = 0.0001 max_buy_btc = 0.1 ask_spread = 0.00 price_ticker_ws_url = "wss://ws.kraken.com" ``` Co-authored-by: binarybaron <you@domain.com> |
||
---|---|---|
.cargo | ||
.github | ||
docs | ||
monero-harness | ||
monero-rpc | ||
monero-wallet | ||
swap | ||
.gitignore | ||
bors.toml | ||
Cargo.lock | ||
Cargo.toml | ||
CHANGELOG.md | ||
CONTRIBUTING.md | ||
dprint.json | ||
LICENSE | ||
README.md | ||
rust-toolchain.toml |
XMR to BTC Atomic Swap
This repository hosts an MVP for atomically swapping BTC to XMR. It implements the protocol described in section 3 of this paper.
More information about the protocol in this presentation and this blog post.
Currently, swaps are only offered in one direction with the swap
CLI on the buying side (send BTC, receive XMR).
We are working on implementing a protocol where XMR moves first, but are currently blocked by advances on Monero itself.
You can read this blogpost for more information.
Quick Start
- Download the latest
swap
binary release for your operating system. - Find a seller to swap with:
./swap --testnet list-sellers
- Swap with a seller:
./swap --testnet buy-xmr --receive-address <YOUR MONERO ADDRESS> --change-address <YOUR BITCOIN CHANGE ADDRESS> --seller <SELLER MULTIADDRESS>
For more detailed documentation on the CLI, see this README.
Becoming a Market Maker
Swapping of course needs two parties - and the CLI is only one of them: The taker that occasionally starts a swap with a market maker.
If you are interested in becoming a market maker you will want to run the second binary provided in this repository: asb
- the Automated Swap Backend.
Detailed documentation for the asb
can be found in this README.
Safety
This software is using cryptography that has not been formally audited. While we do our best to make it safe, it is up to the user to evaluate whether or not it is safe to use for their purposes. Please also see section 15 and 16 of the license.
Keep in mind that swaps are complex protocols, it is recommended to not do anything fancy when moving coins in and out. It is not recommended to bump fees when swapping because it can have unpredictable side effects.
Contributing
We are encourage community contributions whether it be a bug fix or an improvement to the documentation. Please have a look at the contribution guidelines.
Rust Version Support
Please note that only the latest stable Rust toolchain is supported. All stable toolchains since 1.58 should work.
Contact
Feel free to reach out to us in the COMIT-Monero Matrix channel.