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.
bcbc5166aaf97f182fa83761b6b387de04c50e716e2c19b49525b185ef87b633
Both payments are on their chains and locked to the same secret hash b182ef905526607b61969d4aed15f7b78350559b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: bcbc5166aaf97f182fa83761b6b387de04c50e716e2c19b49525b185ef87b633
- MakerPaymentSpent: a0ee4480c21764801bcd8ff3e87873dfbae054aee62c159659db019e5b451944
02833964ccf8d886f0d2df9fc2369fa772413b547675eeaae173008199e63c68
Both payments are on their chains and locked to the same secret hash b182ef905526607b61969d4aed15f7b78350559b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: f770b730fbffb126a9296e34290bae6300ef76e6cd0d31e36218b6af9c2f3cff
- TakerPaymentSent · TakerPaymentReceived: 02833964ccf8d886f0d2df9fc2369fa772413b547675eeaae173008199e63c68
- TakerPaymentSpent: 8bf31067a26d17136ed44c83a3552084f53400a03d8e448bf3f276fa07585140
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.