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 1781534851 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 99ae532bda37ff7074677252a2d963ccaeeaa25992137d4800f37d783f477700. Checked 2026-09-24 01:56:29 UTC.
20f032833a9c5bdaba6e50ea6faf7aea666a76941921d999dc94632c4684758c
Both payments are on their chains and locked to the same secret hash 8136ea11f3b3bdfa7e1cbcd3ce91364f72271a83, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 20f032833a9c5bdaba6e50ea6faf7aea666a76941921d999dc94632c4684758c
- MakerPaymentSpent: 99ae532bda37ff7074677252a2d963ccaeeaa25992137d4800f37d783f477700
fb0cf56f2f633a92441b89f9690cbf1defb3cfa422ea688e384a5622bf587208
Both payments are on their chains and locked to the same secret hash 8136ea11f3b3bdfa7e1cbcd3ce91364f72271a83, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: ee019625795578c6ec62dc29564bebbbaf49e0901abc49f7bb0e29c505c182a4
- TakerPaymentSent · TakerPaymentReceived: fb0cf56f2f633a92441b89f9690cbf1defb3cfa422ea688e384a5622bf587208
- TakerPaymentSpent: febf731da9aeb79b76ba8fe9e6c9e48ba707f9766831e95e6e3fae5c27ac4fa0
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.