CoinSwapCS
CoinSwapCS copied to clipboard
AdamISZ
Simple implementation of Bitcoin CoinSwap, client-server
Currently use a not-in-config file `cs_single().one_confirm_timeout` value for the timeout of the state transition `CoinSwapCarol.receive_tx4_sig` which is set to 7200 (2 hours) currently. So there are two things that crop...
Code currently hardcodes mixdepth 0 as funding depth and mixdepth 1 as destination. It's nice to have a simple default for easier configuration, but e.g. people with existing joinmarket wallets...
Currently the TX0/TX1 transactions are normal looking bitcoin transactions, N inputs from a wallet to 1 output and 1 change. The TX4/TX5 spends out to a single address; either sourced...
For attempting to mix in with the larger anonymity set, it is obviously unhelpful that in the simplest form, a coinswap will consist of 2 pairs of transactions of (a)...
In cooperative case we have paths (wallet)-> p2sh 2 of 2 -> (other wallet). This "hides" in the anonymity set of all 2 of 2 addresses (with huge caveat of...
I tried to go over the protocol and insert bullets in between phases where a chain reorg might happen. The naming and numbering can be seen [here for Alice](https://github.com/AdamISZ/CoinSwapCS/blob/master/coinswap/alice.py#L27-L51) and...
See https://github.com/JoinMarket-Org/joinmarket/issues/335 for ideas about CoinSwap on Joinmarket. For now this repo is being deliberately done in the simplest way I can imagine, with an HTTP JSON-RPC interface. There is...
At the moment only a ghost of this idea in the handshake/config (`source_chain`, `destination_chain`, currently only BTC supported). This will obviously be a bit difficult depending on the other chain,...
This is more blue-sky thinking for now, but a client may want to assess the utxos it's going to be provided in a swap. Doing this without creating a snooping...