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.
31c5f12bf23540dca95ee0e76d756b282d3b0772f4eaeca91ffdcd5b58e564d5
Both payments are on their chains and locked to the same secret hash 30eb4cac32fb1ea0e043d7b7e7010b037dec307f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 31c5f12bf23540dca95ee0e76d756b282d3b0772f4eaeca91ffdcd5b58e564d5
- MakerPaymentSpent: 95f2241a4b622dc92573cc1bc270f6254450f31118bfa0b2158ca74f54a3e6ae
8762d8a0b3b0f96c270f10780033ceffd76a218029a8a49b20118b8593b9f363
Both payments are on their chains and locked to the same secret hash 30eb4cac32fb1ea0e043d7b7e7010b037dec307f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7b5c548132e98f4ef14c538a7a2579e9e6b7931b04a1bd73f4b653ea573c2d2b
- TakerPaymentSent · TakerPaymentReceived: 8762d8a0b3b0f96c270f10780033ceffd76a218029a8a49b20118b8593b9f363
- TakerPaymentSpent: 335e3cd8a38d8c46b78ee5d2cb483ee44d8af28de95deac044e99adcd520c252
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.