Bitcoin–Monero Cross-chain Atomic Swap

atomic-swap bitcoin hacktoberfest monero rust

You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Go to file

rishflab a0ef1f96ec Replace bitcoind wallet with bdk wallet The bitcoind wallet required the user to run a bitcoind node. It was replaced with a bdk wallet which allows the user to connect to an electrum instance hosted remotely. An electrum and bitcoind testcontainer were created to the test the bdk wallet. The electrum container reads the blockdata from the bitcoind testcontainer through a shared volume. bitcoind-harness was removed as bitcoind initialisation code was moved into test_utils. The bdk wallet differs from the bitcoind wallet in that it needs to be manually synced with an electrum node. We synchronise the wallet once upon initialisation to prevent a potentially long running blocking task from interrupting protocol execution. The electrum HTTP API was used to get the latest block height and the transaction block height as this functionality was not present in the bdk wallet API or it required the bdk wallet to be re-synced to get an up to date value.		3 years ago
.github/workflows	Remove tor installation from CI	3 years ago
docs	The first message is actually a quote or rate request	3 years ago
monero-harness	Remove newline in use statements	3 years ago
swap	Replace bitcoind wallet with bdk wallet	3 years ago
.gitignore	Push cargo lock to git as we are building a binary	4 years ago
.mergify.yml	Add Mergify rule to delete merged branch and bors+	3 years ago
BTC_XMR_atomic_swap_protocol.svg	Fix embedded image	4 years ago
Cargo.lock	Replace bitcoind wallet with bdk wallet	3 years ago
Cargo.toml	Merge xmr_btc crate	3 years ago
LICENSE	Change license to GPLv3	4 years ago
README.md	Fix typo	4 years ago
bors.toml	Fix typo	3 years ago
rust-toolchain	Upgrade toolchain	3 years ago
rustfmt.toml	Upgrade toolchain	3 years ago

README.md

XMR to BTC Atomic Swap

This repository is a proof of concept for atomically swapping XMR for BTC.

We define:

Alice to be the actor that initially holds XMR.
Bob to be the actor that initially holds BTC.

In the best-case scenario the protocol looks like this:

Alice and Bob exchange a set of addresses, keys, zero-knowledge proofs and signatures.
Bob publishes Tx_lock, locking up his bitcoin in a 2-of-2 multisig output owned by Alice and Bob. Given the information exchanged in step 1, Bob can refund his bitcoin if he waits until time t_1 by using Tx_cancel and Tx_refund. If Bob doesn't refund after time t_1, Alice can punish Bob for being inactive by first publishing Tx_cancel and, after t_2, spending the output using Tx_punish.
Alice sees that Bob has locked up the bitcoin, so she publishes Tx_lock on the Monero blockchain, locking up her monero in an output which can only be spent with a secret key owned by Alice (s_a) and a secret key owned by Bob (s_b). This means that neither of them can actually spend this output unless they learn the secret key of the other party.
Bob sees that Alice has locked up the monero, so he now sends Alice a missing key bit of information which will allow Alice to redeem the bitcoin using Tx_redeem.
Alice uses this information to spend the bitcoin to an address owned by her. When doing so she leaks her Monero secret key s_a to Bob through the magic of adaptor signatures.
Bob sees Alice's Tx_redeem on Bitcoin, extracts Alice's secret key from it and combines it with his own to spend the monero to an address of his own.

The repository is structured as a library and a single test function that executes the swap. The library has the following modules:

alice: Defines the state machine that describes the swap for Alice. This includes the messages sent to/from Alice.
bob: Defines the state machine that describes the swap for Bob. This includes the messages sent to/from Bob.
bitcoin: Keys, signing functions, transactions etc. for Bitcoin. Also includes a test wallet (see below).
monero: Keys, signing functions, transactions etc. for Monero. Also includes a test wallet (see below).

Currently we have a single test function that proves the following:

Interaction with both block chains and their respective wallets works.
The messages required are correct and can manually drive the state transitions to execute a swap.
It is possible to interact with, and watch, the monero blockchain using monero-wallet-rpc.
It is possible to watch a bitcoind instance using bitcoin-harness (we already knew this :)

Currently we do not do:

Actual network communication.
Verification that the UI is acceptable. Since we do everything in a single test function there is no user interaction, this is unrealistic for a real product.

Testing

We wrote a few additional libraries to facilitate testing:

Wallets

bitcoin module contains a test wallet by way of bitcoind.
monero: module contains a test wallet by way of monero-wallet-rpc.

Blockchain harnesses

We have written two harnesses for interacting with bitcoin and monero.

These harnesses wrap interaction with bitcoind and monerod/monero-wallet-rpc.

We use testcontainers-rs to spin up bitcoind, monerod, and monero-wallet-rpc in docker containers during unit/integration testing.