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.
148f4eade6806a595cdb2d15c7d4d5d59144ecad495c4c6c3b67ab2da7ffea87
Both payments are on their chains and locked to the same secret hash 1e30ea7c7fe3f0d32671d0770cb500c8327d819d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 148f4eade6806a595cdb2d15c7d4d5d59144ecad495c4c6c3b67ab2da7ffea87
- MakerPaymentSpent: c0f0fd54118cd99dad5354ef3d866c6086ea227bcf47b7767559f779f021e2a6
a50eb7a6efc6101d189e8a1f1c77b7802ece8b8bb8e082fef80094eed6871db4
Both payments are on their chains and locked to the same secret hash 1e30ea7c7fe3f0d32671d0770cb500c8327d819d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6d0ee2117d7a45d4aecd0d0ee71ea3ee68948706fdc6a87e9812704775f4c468
- TakerPaymentSent · TakerPaymentReceived: a50eb7a6efc6101d189e8a1f1c77b7802ece8b8bb8e082fef80094eed6871db4
- TakerPaymentSpent: 6fb0cc8e8f2aa31a42bf67c6e615cca8749985a0b8db4015f3245d18e1653950
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.