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:1959] !wait for maker payment spend confirmations: rpc_clients:112] Waited too long until 1757875066 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 93849918e5bf1e3121b57de7dbf3371bf1cbe8be531008a42a5bddfc57b14c0a. Checked 2026-09-22 12:54:12 UTC.
4aedfd0a38d5f9f0f47df9244fc6772c9ff11c666e434a46a4885a6c0913e30d
Both payments are on their chains and locked to the same secret hash 5aaa31bd39487d59eaba4f3fac6cce4eaa22630d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4aedfd0a38d5f9f0f47df9244fc6772c9ff11c666e434a46a4885a6c0913e30d
- MakerPaymentSpent: 93849918e5bf1e3121b57de7dbf3371bf1cbe8be531008a42a5bddfc57b14c0a
2c859cd905cd3ef149f5310c9605c9f9daa26a0c22ceef62fba8f11835b891e0
Both payments are on their chains and locked to the same secret hash 5aaa31bd39487d59eaba4f3fac6cce4eaa22630d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 84327c63a9fcc4dea64e6615097d4a9da0b101e287fe4b1089d30f9819fafd83
- TakerPaymentSent · TakerPaymentReceived: 2c859cd905cd3ef149f5310c9605c9f9daa26a0c22ceef62fba8f11835b891e0
- TakerPaymentSpent: a6fcfd89bac9354df976c736f09af016fba415209044e804103b18669db8d527
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.