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.
587cafb7f74df783c8f531e86439d0282d43037a7c6fe866c46bc9ba900b7cc4
Both payments are on their chains and locked to the same secret hash bb8eb43d9f8f67379128a5a5772b2f6fa5ad310c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 587cafb7f74df783c8f531e86439d0282d43037a7c6fe866c46bc9ba900b7cc4
dee44bd6c613f427f4c07ce7686be4c769746dbc8979e7574fa726ffd52ea2f1
Both payments are on their chains and locked to the same secret hash bb8eb43d9f8f67379128a5a5772b2f6fa5ad310c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: bc8d6022dc3aaba88ec240213db524eb257cf834fba4ce48c8955dafa696d2ba
- TakerPaymentReceived: dee44bd6c613f427f4c07ce7686be4c769746dbc8979e7574fa726ffd52ea2f1
- TakerPaymentSpent: dc85816033066e70e467456c10dde5afb9415f185de39d5a9d63a1fdf6fb3e9f
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.