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 1777028948 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 84239ddd93b5f360b020cc1abdfcffc6ef3404490a8a0fdc174578648289d153. Checked 2026-09-24 02:06:26 UTC.
cd018c43a44ca6eb4bd09941dfd7b3ab5582704ff5e8c7772e7438f5156d406e
Both payments are on their chains and locked to the same secret hash 42ab639010755eb0469c0ed117d485863931a1e2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cd018c43a44ca6eb4bd09941dfd7b3ab5582704ff5e8c7772e7438f5156d406e
- MakerPaymentSpent: 84239ddd93b5f360b020cc1abdfcffc6ef3404490a8a0fdc174578648289d153
9cd002d1721a743b9b0555415f464870cbb9672a000afa7e20945d165d969471
Both payments are on their chains and locked to the same secret hash 42ab639010755eb0469c0ed117d485863931a1e2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 22a0a1d0d67c32f0be7daa8f61348e4b913b3e63ef3aa881c4cb73da174e9d89
- TakerPaymentSent · TakerPaymentReceived: 9cd002d1721a743b9b0555415f464870cbb9672a000afa7e20945d165d969471
- TakerPaymentSpent: 1c5cad93a45da4053e18a76715443a5a812ab9b2075cb67d4eed661292e0f4b1
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.