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 1777137383 for transaction to be confirmed 7 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 a8e266a2a0792147283a70d2ed9f291bd2736ed0a9ca2b52af6117a75678ad00. Checked 2026-09-24 02:06:21 UTC.
f044938cfd8b93434ef83ec9b19dd80252451769f03ab2ba405087f4cd2c6c85
Both payments are on their chains and locked to the same secret hash aa8713b0047de0142e708657da2a9df472f8f499, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f044938cfd8b93434ef83ec9b19dd80252451769f03ab2ba405087f4cd2c6c85
- MakerPaymentSpent: a8e266a2a0792147283a70d2ed9f291bd2736ed0a9ca2b52af6117a75678ad00
3a1bde25158e43b66aa3c6f00f0c7185f174fbbad1752c908284cbc440371a83
Both payments are on their chains and locked to the same secret hash aa8713b0047de0142e708657da2a9df472f8f499, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8b901c6ed9fb7285eceb378c053d63eb0e0fb12d6f42ef0e4f5fc23437612ac2
- TakerPaymentSent · TakerPaymentReceived: 3a1bde25158e43b66aa3c6f00f0c7185f174fbbad1752c908284cbc440371a83
- TakerPaymentSpent: 8d57b327c98bb0d2a182da53f40c974d64e3e0338f7637dd485d57d20f1df679
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.