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 1782693979 for transaction to be confirmed 1 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 670c331e9d70133721dd5c5c3c44c28969f8a20c6931e07b3a27489d7c26e206. Checked 2026-09-22 12:38:57 UTC.
b69e26643e78f95664d436e3752536a306e2295523fa9cd28f9afb9132bf0697
Both payments are on their chains and locked to the same secret hash 41d228d6ef0faa999fe3f5aeb8edeb5e130c576c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b69e26643e78f95664d436e3752536a306e2295523fa9cd28f9afb9132bf0697
- MakerPaymentSpent: 670c331e9d70133721dd5c5c3c44c28969f8a20c6931e07b3a27489d7c26e206
340be675726e372a0132ff9094a00e382efa6874dfb4af52c28a78179915eaf4
Both payments are on their chains and locked to the same secret hash 41d228d6ef0faa999fe3f5aeb8edeb5e130c576c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ef25c4120d95768c99b48b94e465787f4952019a2b0bf07cbbfc4a848b7b124c
- TakerPaymentSent · TakerPaymentReceived: 340be675726e372a0132ff9094a00e382efa6874dfb4af52c28a78179915eaf4
- TakerPaymentSpent: c9f6af61ad03a48e731762b2a9e53c793f1553f8085786626f85b172e4e71975
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.