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 1771179446 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 4908781fefe664d982149365f8cf52fb64de5dd0e584ac2d5a52435c4733151d. Checked 2026-09-22 12:42:48 UTC.
a8f172f4275c3c8a5ed448e555d08fa34e766648e94027a39ba1d38e3d32f725
Both payments are on their chains and locked to the same secret hash 167d9af88d3b184ae94731c0d0d9ee5e6d1ff104, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a8f172f4275c3c8a5ed448e555d08fa34e766648e94027a39ba1d38e3d32f725
- MakerPaymentSpent: 4908781fefe664d982149365f8cf52fb64de5dd0e584ac2d5a52435c4733151d
24a44a8cf2f5603d7f030d414e8f346853a47aa1dc81f60bd30367080bade009
Both payments are on their chains and locked to the same secret hash 167d9af88d3b184ae94731c0d0d9ee5e6d1ff104, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 154749f0b7fb3e8788b22c0f7ba6bbcf127fb17f4f215d4355df3c55ddbe2339
- TakerPaymentSent · TakerPaymentReceived: 24a44a8cf2f5603d7f030d414e8f346853a47aa1dc81f60bd30367080bade009
- TakerPaymentSpent: d5b48879c633d510f60624d3aa9e3e65dec2ed2dc6cfaabfba75de7e2e86aff2
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.