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.
bafe3e1ccc6a3091ffb527eaab753f678f9133d4fba95188f49477093831041b
Both payments are on their chains and locked to the same secret hash 37c227296123525a71a991fe8c1dcdd1a49ff7b8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: bafe3e1ccc6a3091ffb527eaab753f678f9133d4fba95188f49477093831041b
54287d2404482ccd6c40751797f85b27e1a7c05296d9378159ef5efdb3204b10
Both payments are on their chains and locked to the same secret hash 37c227296123525a71a991fe8c1dcdd1a49ff7b8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: ec6e7b1e61e728bf62b747f5ea078669fe347c55019484b0c2bfef55babb1fc2
- TakerPaymentReceived: 54287d2404482ccd6c40751797f85b27e1a7c05296d9378159ef5efdb3204b10
- TakerPaymentSpent: 16c814fcedbc98d7a9f6e0b57b3b782e7634b845f66a57061f222a977a982d6a
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.