c976358c37
- Swap-id is exchanged during execution setup. CLI (Bob) sends the swap-id to be used in his first message. - Transfer poof and encryption signature messages include the swap-id so it can be properly associated with the correct swap. - ASB: Encryption signatures are associated with swaps by swap-id, not peer-id. - ASB: Transfer proofs are still associated to peer-ids (because they have to be sent to the respective peer), but the ASB can buffer multiple - CLI: Incoming transfer proofs are checked for matching swap-id. If a transfer proof with a different swap-id than the current executing swap is received it will be ignored. We can change this to saving into the database. Includes concurrent swap tests with the same Bob. - One test that pauses and starts an additional swap after the transfer proof was received. Results in both swaps being redeemed after resuming the first swap. - One test that pauses and starts an additional swap before the transfer proof is sent (just after BTC locked). Results in the second swap redeeming and the first swap being refunded (because the transfer proof on Bob's side is lost). Once we store transfer proofs that we receive during executing a different swap into the database both swaps should redeem. Note that the monero harness was adapted to allow creating wallets with multiple outputs, which is needed for Alice. |
||
|---|---|---|
| .cargo | ||
| .github | ||
| docs/asb | ||
| monero-harness | ||
| monero-rpc | ||
| swap | ||
| tokio-tar | ||
| .dprintrc.json | ||
| .gitignore | ||
| bors.toml | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| LICENSE | ||
| README.md | ||
| rust-toolchain | ||
| rustfmt.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.
Quick start - CLI
- Download the latest
swapbinary release for your operating system - Run the binary specifying the monero address where you wish to receive monero and the connection details of the seller:
./swap buy-xmr --receive-address <YOUR MONERO ADDRESS> --seller-peer-id <SELLERS PEER ID> --seller-multiaddr <SELLERS MULTIADDRESS>You can generate a receive address using your monero wallet. The seller will provide you their peer id and multiaddress. We are running anasbinstance on testnet. You can swap with to get familiar with theswapCLI. Our peer id is12D3KooWCdMKjesXMJz1SiZ7HgotrxuqhQJbP5sgBm2BwP1cqThiand our multiaddress is/dns4/xmr-btc-asb.coblox.tech/tcp/9876 - Follow the instructions printed to the terminal
Limitations
For now, the MVP is limited to testnet3 on Bitcoin and stagenet on Monero.
How it works
This repository primarily hosts two components:
- the
swapCLI - the
asbservice
swap CLI
The swap CLI acts in the role of Bob and swaps BTC for XMR.
See ./swap --help for a description of all commands.
The main command is buy-xmr which automatically connects to an instance of asb.
asb service
asb is short for automated swap backend (we are open to suggestions for better names!).
The service acts as the counter-party for the swap CLI in the role of Alice.
It provides the CLI with a quote and the liquidity necessary for swapping BTC into XMR.
For details on how to run the ASB please refer to the ASB docs.
Contact
Feel free to reach out to us in the COMIT-Monero Matrix channel.