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.
e0c5760c4efa704489347077b5ee29cc08d589cf714518dd1310610efcaef0db
Both payments are on their chains and locked to the same secret hash ade77aeffa8fd74203a57986669bf0f34d5f2fa7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e0c5760c4efa704489347077b5ee29cc08d589cf714518dd1310610efcaef0db
- MakerPaymentSpent: abde100603ab9ab29fa3a9054a29115a4b18b9dfafb23ac514cb76f328f8929d
ddf927a9a7b1e2288c993c7ff4810b775b42ac68e38501fbe8395dc37cde8770
Both payments are on their chains and locked to the same secret hash ade77aeffa8fd74203a57986669bf0f34d5f2fa7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8c4988f440c6e5232b723fe8970e3e6663abdcb79ee16fd20bcbcf9827e8ef26
- TakerPaymentSent · TakerPaymentReceived: ddf927a9a7b1e2288c993c7ff4810b775b42ac68e38501fbe8395dc37cde8770
- TakerPaymentSpent: 46b1129df9a5c1f4053f50633243a61fdb7709523ed7a3b5fa9ee5291f8fe5b6
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.