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.
780d72ac4a4a269bfc8d0157e3e9e70c86b978a8334278df1e656e4ac7e40a7c
Both payments are on their chains and locked to the same secret hash 2ce03dc46bff2db06d7226e15ae705c32a8b644a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 780d72ac4a4a269bfc8d0157e3e9e70c86b978a8334278df1e656e4ac7e40a7c
- MakerPaymentSpent: c49e6c3fe2cdb6d12c9453a3ce3b8dca41429ffb8d6d4b85adb87fe6bfa228e1
c74ce7753f286ef36163698751a295a84a2a27964de19fa79d664c735c99cf94
Both payments are on their chains and locked to the same secret hash 2ce03dc46bff2db06d7226e15ae705c32a8b644a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ebdde379bcb3c48ebe1dfa7f20c4bbb29a7dffee1230ed400cdb2dc131b0f216
- TakerPaymentSent · TakerPaymentReceived: c74ce7753f286ef36163698751a295a84a2a27964de19fa79d664c735c99cf94
- TakerPaymentSpent: 66dec3d7f6d8b6394b440f1c848891c59f2b756925747941029d801c0c1f9a27
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.