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.
eb3db7735c7a61ea29ae7c3a0805e22e00984e309bde6bba8c74d1c1cf3f15a8
Both payments are on their chains and locked to the same secret hash 6e3cf34ac63bc74aa88249d46ece7ec43ddaad06, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived: eb3db7735c7a61ea29ae7c3a0805e22e00984e309bde6bba8c74d1c1cf3f15a8
- MakerPaymentSpent: d088750743259c7e309e94d85cbdb538ed6f6038cfef591c49b34957987136bd
a12834daa7d7b6b2cca5ea113e700d4c00f0d34632d4038b304dc2b9cfcb7676
Both payments are on their chains and locked to the same secret hash 6e3cf34ac63bc74aa88249d46ece7ec43ddaad06, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent: 95bf3c83152f1a5eb5ae72bf22e47b8a1e0132085da3fc7215e70a4a3518354e
- TakerPaymentSent: a12834daa7d7b6b2cca5ea113e700d4c00f0d34632d4038b304dc2b9cfcb7676
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.