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:2050] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1767214529 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 0a80ae79c1eba9f6e3fc75671adee747a8b0e540cbb89314b98d28d5c7c2dbb7. Checked 2026-09-22 12:45:42 UTC.
2fb5bb63446e9251fc9eff95b2184ec07def878e738154c9568a928f3b8b3ffd
Both payments are on their chains and locked to the same secret hash cbab693516fa8aa1388d07d25f29cd25710179df, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2fb5bb63446e9251fc9eff95b2184ec07def878e738154c9568a928f3b8b3ffd
- MakerPaymentSpent: 0a80ae79c1eba9f6e3fc75671adee747a8b0e540cbb89314b98d28d5c7c2dbb7
daf2d5ea0c61e39f9026936c9fb6ec6195cc57d9a1a07669bd5bfcb3b0517479
Both payments are on their chains and locked to the same secret hash cbab693516fa8aa1388d07d25f29cd25710179df, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 49bc7c296c6e0451787a751df8c532a523de954791db4526a3d3177cdb1b4d27
- TakerPaymentSent · TakerPaymentReceived: daf2d5ea0c61e39f9026936c9fb6ec6195cc57d9a1a07669bd5bfcb3b0517479
- TakerPaymentSpent: edaecd4d7eab0e2e81c75c9aa37d676fa0df2504daab5f67f58c62ce64ece025
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.