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 1786928002 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 8d16eda2f2743fb7ec80428000f16dbe445dad308e6ac831b97e3f5fbacf8cb1. Checked 2026-09-24 01:56:04 UTC.
88b06485a402f81b34ee8e4ba73dae4e3c60973940b3041a1c542b1b551844d8
Both payments are on their chains and locked to the same secret hash dd18e4ef610d38c8c293e86ac2bca38e320eb25c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 88b06485a402f81b34ee8e4ba73dae4e3c60973940b3041a1c542b1b551844d8
- MakerPaymentSpent: 8d16eda2f2743fb7ec80428000f16dbe445dad308e6ac831b97e3f5fbacf8cb1
d0e7b51c4f837c565b97683202dc92ead17b9813617b7c7fd9759b5168a09160
Both payments are on their chains and locked to the same secret hash dd18e4ef610d38c8c293e86ac2bca38e320eb25c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3b47f8e17018dbc370393be3421430e7d1d12d7af7651ec6520b82d14131ec52
- TakerPaymentSent · TakerPaymentReceived: d0e7b51c4f837c565b97683202dc92ead17b9813617b7c7fd9759b5168a09160
- TakerPaymentSpent: 3e77db15c9fd99406ce060f5dfacc4c04328e314ca5710eedcad2bf5e3940bf0
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.