Git-Mirrors/xmr-btc-swap
1
0
Fork 0
mirror of https://github.com/comit-network/xmr-btc-swap.git synced 2024-10-01 01:45:40 -04:00
Code Issues Packages Projects Releases Wiki Activity
ee90c228b4
xmr-btc-swap/bors.toml

23 lines
1.1 KiB
TOML
Raw Normal View History

Swap Monero for Bitcoin Co-authored-by: rishflab <rishflab@hotmail.com> Co-authored-by: Philipp Hoenisch <philipp@hoenisch.at> Co-authored-by: Tobin C. Harding <tobin@coblox.tech>
2020-09-28 02:18:50 -04:00
status = [
"static_analysis",
Update bors config Add armv build check to bors. Update build and test names due to matix configuration changes.
2021-03-15 01:04:14 -04:00
"build (x86_64-unknown-linux-gnu, ubuntu-latest)",
"build (armv7-unknown-linux-gnueabihf, ubuntu-latest)",
"build (x86_64-apple-darwin, macos-latest)",
"build (x86_64-pc-windows-msvc, windows-latest)",
Simplify matrix for test job
2021-03-24 01:02:43 -04:00
"test (ubuntu-latest)",
"test (macos-latest)",
Updates bors to include all docker tests
2021-01-28 17:20:08 -05:00
"docker_tests (happy_path)",
Remove connection handling from swap execution The swap should not be concerned with connection handling. This is the responsibility of the overall application. All but the execution-setup NetworkBehaviour are `request-response` behaviours. These have built-in functionality to automatically emit a dial attempt in case we are not connected at the time we want to send a message. We remove all of the manual dialling code from the swap in favor of this behaviour. Additionally, we make sure to establish a connection as soon as the EventLoop gets started. In case we ever loose the connection to Alice, we try to re-establish it.
2021-03-18 03:00:02 -04:00
"docker_tests (happy_path_restart_bob_after_xmr_locked)",
Alice resumes swaps
2021-03-26 00:38:30 -04:00
"docker_tests (happy_path_restart_alice_after_xmr_locked)",
Remove connection handling from swap execution The swap should not be concerned with connection handling. This is the responsibility of the overall application. All but the execution-setup NetworkBehaviour are `request-response` behaviours. These have built-in functionality to automatically emit a dial attempt in case we are not connected at the time we want to send a message. We remove all of the manual dialling code from the swap in favor of this behaviour. Additionally, we make sure to establish a connection as soon as the EventLoop gets started. In case we ever loose the connection to Alice, we try to re-establish it.
2021-03-18 03:00:02 -04:00
"docker_tests (happy_path_restart_bob_before_xmr_locked)",
Fix typo
2021-02-09 20:06:41 -05:00
"docker_tests (bob_refunds_using_cancel_and_refund_command)",
"docker_tests (bob_refunds_using_cancel_and_refund_command_timelock_not_expired_force)",
Re-introduce punish test
2021-03-16 02:18:57 -04:00
"docker_tests (bob_refunds_using_cancel_and_refund_command_timelock_not_expired)",
Alice resumes swaps
2021-03-26 00:38:30 -04:00
"docker_tests (punish)",
Test Alice refunds if restarted and Bob refunded
2021-04-01 02:36:45 -04:00
"docker_tests (alice_punishes_after_restart_punish_timelock_expired)",
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.
2021-04-08 04:56:26 -04:00
"docker_tests (alice_refunds_after_restart_bob_refunded)",
"docker_tests (ensure_same_swap_id)",
"docker_tests (concurrent_bobs_after_xmr_lock_proof_sent)",
"docker_tests (concurrent_bobs_before_xmr_lock_proof_sent)"
Swap Monero for Bitcoin Co-authored-by: rishflab <rishflab@hotmail.com> Co-authored-by: Philipp Hoenisch <philipp@hoenisch.at> Co-authored-by: Tobin C. Harding <tobin@coblox.tech>
2020-09-28 02:18:50 -04:00
]
Reference in New Issue Copy Permalink