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.
d00269fc062a3a3cb48bc24c8a5470e9ee37bf3614d7a0f1aca44266881ef82b
Both payments are on their chains and locked to the same secret hash 05a436a77d93375cf1b24854114f8754ca6ca661, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d00269fc062a3a3cb48bc24c8a5470e9ee37bf3614d7a0f1aca44266881ef82b
- MakerPaymentSpent: 41f5285b8594f4dc7cc597ff80ecb044aa6b08a8366bfde8b4145f61e011681b
d791e3c866ea9765764c5876be037c56933f15870a66c79937ecc3f248b5d28c
Both payments are on their chains and locked to the same secret hash 05a436a77d93375cf1b24854114f8754ca6ca661, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: a251885f93e98f4f4bf0ce63f46b750e53bbdd864b833da2151048bc833cd5cf
- TakerPaymentSent · TakerPaymentReceived: d791e3c866ea9765764c5876be037c56933f15870a66c79937ecc3f248b5d28c
- TakerPaymentSpent: 06c9c9d2bef1f18f7313183b89fd6a2ee57bac1b6a99c6d92011f76a2b95d06a
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.