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 1785266156 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 6661cb99c158adcb440d2feb1f1605df5ba91f0e649a95b291d7fa9c08b03b33. Checked 2026-09-24 01:56:12 UTC.
b88459f3da3288ae8ded9a0e765bb7dcdfcb99c8d430fa91b7a7875b912cab5c
Both payments are on their chains and locked to the same secret hash 2c6461db68f4fb11a04091bf792c0099e08bf205, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b88459f3da3288ae8ded9a0e765bb7dcdfcb99c8d430fa91b7a7875b912cab5c
- MakerPaymentSpent: 6661cb99c158adcb440d2feb1f1605df5ba91f0e649a95b291d7fa9c08b03b33
fabdef9bb5d24ddfba289b144a5b4db969db4f0c94ec7b9a13937cb8e8e2753e
Both payments are on their chains and locked to the same secret hash 2c6461db68f4fb11a04091bf792c0099e08bf205, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a673696f03137a286ae851d1c7fb99473460662653082ce7fe8e3984f498b30e
- TakerPaymentSent · TakerPaymentReceived: fabdef9bb5d24ddfba289b144a5b4db969db4f0c94ec7b9a13937cb8e8e2753e
- TakerPaymentSpent: aced706a00bb9c8d94d02e378a4a5695f8e138066f867e0c168ff5742d01e524
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.