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.
a585b1210105e6776d88a7e1f2289eacdc301ddc5a6d20b5cc182a9e4b7f7054
Both payments are on their chains and locked to the same secret hash 7cad0f4b013c2896d01f67794772ee23480d46f5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived: a585b1210105e6776d88a7e1f2289eacdc301ddc5a6d20b5cc182a9e4b7f7054
- MakerPaymentSpent: c142a130a70ae7ecdbcd21f7b367c0857174ff84490be3a7026d0ea561f2064e
ecdc9802eba4194e809c01e72484211ae0c94c884131cdacf958d6eb8c75a9ae
Both payments are on their chains and locked to the same secret hash 7cad0f4b013c2896d01f67794772ee23480d46f5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent: c796c5e288585f6ce4c482d2425d1bdd45987afea3f98aa92f4d0fb7140d5b37
- TakerPaymentSent: ecdc9802eba4194e809c01e72484211ae0c94c884131cdacf958d6eb8c75a9ae
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.