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.
a2377d9a8cab40ecc530b7ce9f8293b4b2126a7aa7ead02e2a9ced8ff704f080
Both payments are on their chains and locked to the same secret hash dc5f5c99df4eeea829a5022ea946a0adc3c2067c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: a2377d9a8cab40ecc530b7ce9f8293b4b2126a7aa7ead02e2a9ced8ff704f080
61ac21ee5129b69967815839c257e25918683dd38f5eb4e4801ca5dcdbadf512
Both payments are on their chains and locked to the same secret hash dc5f5c99df4eeea829a5022ea946a0adc3c2067c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 2baf18fb6d41050f1194c9233b65f11269cc0e61333a47bda4d8f3bd24163d07
- TakerPaymentReceived: 61ac21ee5129b69967815839c257e25918683dd38f5eb4e4801ca5dcdbadf512
- TakerPaymentSpent: 218c8585d804ad324e0833bac47ecf7a9fedcc67ad8f8121f85aee5ac8034c40
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.