An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.
f93ae889e9e0e0a3bb10a695b08514a69ad8fd9cadfdcb48df7f93b222eb3361
Both payments are on their chains and locked to the same secret hash 56a3a388f41abc6ef2be4d2218922a6c40a82cb8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: f93ae889e9e0e0a3bb10a695b08514a69ad8fd9cadfdcb48df7f93b222eb3361
- MakerPaymentSpent: c805364c9c434334ed0f3aa1db4821e7f35fec7e8b36930fa8f142fdef7fc250
25f9e661313fb558e242f00dfddeea37f05cb8733e2a358e2fa0b8f563cd7270
Both payments are on their chains and locked to the same secret hash 56a3a388f41abc6ef2be4d2218922a6c40a82cb8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8134d309092aba828479dec60433a1931560463f9d8062a9648d00f72dbce529
- TakerPaymentSent · TakerPaymentReceived: 25f9e661313fb558e242f00dfddeea37f05cb8733e2a358e2fa0b8f563cd7270
- TakerPaymentSpent: 17e03a2fb66df136b56304d6c17b13b0f07ecc889fe3a09b3b6e5b0c6480c75d
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.