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.
The record stops at MakerPaymentSpendConfirmFailed. The taker's claim on the maker's coin was broadcast but not seen to confirm.
taker_swap:2052] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1777936201 for transaction to be confirmed 2 times
By this step both payments were on their chains and the price had been struck, so the trade counts toward the reference price. The claim can still be made for as long as the payment is unspent, and since the timelock has passed the payer can take it back as well, so whichever lands first settles it. Whether it was retried is a question for the chain rather than for this log.
The chain says the claim landed: the payment was spent with the preimage, in e6408330983b0cf8f9308ce00ec68c3126a1d6f8e5311a000de9829b02cedbe8. Checked 2026-09-24 02:06:13 UTC.
9a0a398f9a6ac0e2c7e8bd8f9fabffac2da77ccdc2e9a40991e199d805734ad9
Both payments are on their chains and locked to the same secret hash 19e32698159f848f6890882f9bb17c41290ca1cb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9a0a398f9a6ac0e2c7e8bd8f9fabffac2da77ccdc2e9a40991e199d805734ad9
- MakerPaymentSpent: e6408330983b0cf8f9308ce00ec68c3126a1d6f8e5311a000de9829b02cedbe8
2b4246db9388743698adea6cd5baa261e8be3df68cf9b4738761db02ba62191f
Both payments are on their chains and locked to the same secret hash 19e32698159f848f6890882f9bb17c41290ca1cb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3bf1efb037bbf3f76179c894cbc1c1fe50628a23ef58c479e22bcc72ca61bec2
- TakerPaymentSent · TakerPaymentReceived: 2b4246db9388743698adea6cd5baa261e8be3df68cf9b4738761db02ba62191f
- TakerPaymentSpent: b94bb35445587436084a9320906e0a9b2ab54b6250d126ae48aa5f8d41527bca
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 defistats-gleec.