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.
4455ba8a197df551d83a33c1d175cb31371e6e806f306cfd9ddd88baacc8f6dc
Both payments are on their chains and locked to the same secret hash b37d293d87f9d39f2a7284b5c41143fb05d33fd2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived: 4455ba8a197df551d83a33c1d175cb31371e6e806f306cfd9ddd88baacc8f6dc
- MakerPaymentSpent: d864c923daf95aa830b8257a0b848d37866262cadc8a44ea87bdae84f9868824
d17c42030fd6f1f36b1c7cc5e8f69f57ea7bba66e3c688833e215edf3f317d0b
Both payments are on their chains and locked to the same secret hash b37d293d87f9d39f2a7284b5c41143fb05d33fd2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent: 7a985c949f573430c25f8f36dff7d3ff7e684d3aa26f354bb8fb51ed75f8fd2e
- TakerPaymentSent: d17c42030fd6f1f36b1c7cc5e8f69f57ea7bba66e3c688833e215edf3f317d0b
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.