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.
bff17fe2003d15c160f568fdaa2a80517053bf677a4c58fbf9abc2b679822972
Both payments are on their chains and locked to the same secret hash 090ff6b4110de47a288a1d67e2751244382af98a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: bff17fe2003d15c160f568fdaa2a80517053bf677a4c58fbf9abc2b679822972
- MakerPaymentSpent: 20820a055fcce957eb8cc72e0b13b3dcf65704ceb758c64cd0b742df06136777
dcdd6af9e7d375d8fb6eac30453cbb647575026d69b0cdae135e42e01800eca7
Both payments are on their chains and locked to the same secret hash 090ff6b4110de47a288a1d67e2751244382af98a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ff3fb61250cf612a39bdbab94f34ac202a27c01bfafcc1a7b1e03160ec44d5fa
- TakerPaymentSent · TakerPaymentReceived: dcdd6af9e7d375d8fb6eac30453cbb647575026d69b0cdae135e42e01800eca7
- TakerPaymentSpent: 32019308f9457850edb21f6e9d9c9b0c46aac00a46829139fa9b216df6b679dc
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.