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 1779646606 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 cd40eb869a74a062e77ec964b586d0c3860cbacc79ac05dedd57497d2c92bef7. Checked 2026-09-24 02:06:04 UTC.
5ab02705fb75b176a4a63937b4bbb9d33c5ebb51805d7aa2476ad6af0c5cf0e6
Both payments are on their chains and locked to the same secret hash 87bbf9455ecf239da2d70c429d1ce6be7a3465ee, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 5ab02705fb75b176a4a63937b4bbb9d33c5ebb51805d7aa2476ad6af0c5cf0e6
- MakerPaymentSpent: cd40eb869a74a062e77ec964b586d0c3860cbacc79ac05dedd57497d2c92bef7
af25439d0dcb2b7160547d63098aedd1c40f70e3801321d3859c012c050dc3ce
Both payments are on their chains and locked to the same secret hash 87bbf9455ecf239da2d70c429d1ce6be7a3465ee, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2d2542d6f69542771dd6205290c564cdb097cfad4c59051236aacf33956ac601
- TakerPaymentSent · TakerPaymentReceived: af25439d0dcb2b7160547d63098aedd1c40f70e3801321d3859c012c050dc3ce
- TakerPaymentSpent: 9549d1b79779d68b44b40268c344a583c8a27331c8514f1734958ce515a48fe4
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.