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.
60a0f1ff75db4ccd0db2cb8796d33185982e93ef64326c59e36a17241a21753f
Both payments are on their chains and locked to the same secret hash 6ff2bc5115738af4ee19ef9c4dc886e501a5d4c9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 60a0f1ff75db4ccd0db2cb8796d33185982e93ef64326c59e36a17241a21753f
7498397eb63b91746e54d096eba15df08aeed36a8f7fe54e1210cc8fa1dc39ee
Both payments are on their chains and locked to the same secret hash 6ff2bc5115738af4ee19ef9c4dc886e501a5d4c9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: c54bab0483aa78625247759840583e00dbb07fe2eb161f1c4fc123bc65f615e1
- TakerPaymentReceived: 7498397eb63b91746e54d096eba15df08aeed36a8f7fe54e1210cc8fa1dc39ee
- TakerPaymentSpent: 25591e66b7aadb1a806ec3eb610a3f7a4fcbfaa11c89bf120f335944577977bf
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.