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:2044] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1764197548 for transaction to be confirmed 5 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 f38d17c5abed0f47e666e0c333a16abe999623d54bd765fda4b64ffd85165d29. Checked 2026-09-22 12:50:14 UTC.
73dd28f14c766d09d81e9ef8128ba1dc3e97f0b61afa9e2ee74aabd21d6e7440
Both payments are on their chains and locked to the same secret hash 185312081e5e78b7d9e3a7da526142dd225193c0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 73dd28f14c766d09d81e9ef8128ba1dc3e97f0b61afa9e2ee74aabd21d6e7440
- MakerPaymentSpent: f38d17c5abed0f47e666e0c333a16abe999623d54bd765fda4b64ffd85165d29
35fee237facbf0bd530674eada19a1485ca941569af454dee69b7a3d30a9a90a
Both payments are on their chains and locked to the same secret hash 185312081e5e78b7d9e3a7da526142dd225193c0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2912ae9f8c928a44e415994c053cb5f249e84316323868d36d610e60a02ad174
- TakerPaymentSent · TakerPaymentReceived: 35fee237facbf0bd530674eada19a1485ca941569af454dee69b7a3d30a9a90a
- TakerPaymentSpent: a1fe94079511729a3b7d2727840379139d52f0f424ba6b3adeafa82316910503
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.