wow
bug/no-rendezvous-windows
dependabot/cargo/serde_cbor-0.11.2
staging
master
dependabot/cargo/tokio-1.10.0
dependabot/cargo/get-port-4.0.0
dependabot/cargo/time-0.3.1
dependabot/cargo/miniscript-6.0.1
feature/allow-monero-wallet-rpc-restart
relay-fee-debug
rendezvous-demo
rendezvous-asb-refactor
rendezvous-cli
swap-setup-proto-rishab
cleanup-module-boundaries
debug-remodel-tor
swap-setup-proto
discover-makers-cli
quote-protocol-refactor
debug-remodel-tor-same-port
small-ux-improvements
quote-websocket
random-branch
xmr-adaptor-signatures
xmr-adaptor-signatures-publish-on-testnet
refactor-network-code
no-transfer-proof-failure
on-chain-protocol
remove-bytes-serde-module
xpub-wallet
remodel-tor
quad9-dns
simplify-eventloop
quote-protocol-libp2p-relay
black-magic
static-linking
asb-configurable-monero-wallet
asb-systemd-setup
idempotent-lock-xmr
simple-state-machine
sort-history-by-height
renew-connection-on-transient-errors
rename-swap-cli
tx-fee
manual-sync
fix-confirmations
deposit
bdk2
nectar
remove-lib-rs
reset-config-command
emulate-blockchain
test-refactor
demo
v0.3
v0.2
v0.1
preview
0.8.1
0.8.0
0.7.0
0.6.0
0.5.0
0.4.0
${ noResults }
1 Commits (c976358c374184c62ea3e08b0d55637f2b0a9899)
Author | SHA1 | Message | Date |
---|---|---|---|
Daniel Karzel |
c976358c37
|
Multiple swaps with the same peer
- 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. |
3 years ago |