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 1781462442 for transaction to be confirmed 3 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 bce4ec93895eff3999cfa4799b6d2bb8730b0cec69fb7e9502ec6dd9b22d1ea8. Checked 2026-09-24 01:56:31 UTC.
eabe6d5a74e9689418e5e876443acbad7eabd43fd59354536b8eb17501cc9524
Both payments are on their chains and locked to the same secret hash 4c59e39715815d04bf4e810cfc1ef1c53e0a9c8c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: eabe6d5a74e9689418e5e876443acbad7eabd43fd59354536b8eb17501cc9524
- MakerPaymentSpent: bce4ec93895eff3999cfa4799b6d2bb8730b0cec69fb7e9502ec6dd9b22d1ea8
93e1ee0a748e3c6c2b3b32b732a3136b11c306d9628dc82d595f9ab6a0103702
Both payments are on their chains and locked to the same secret hash 4c59e39715815d04bf4e810cfc1ef1c53e0a9c8c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 564197f8dd513fa1fde7b160a548273eef0f25cdce52c583abcce9152a818cdf
- TakerPaymentSent · TakerPaymentReceived: 93e1ee0a748e3c6c2b3b32b732a3136b11c306d9628dc82d595f9ab6a0103702
- TakerPaymentSpent: 0590eb2a51740690db1439e82de39dd09b30880cd4088c192eb02bbe9eff3cf9
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.