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 1787944557 for transaction to be confirmed 5 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 68530b595873a1dd36d34ad4470ccb3a5b04ba9b87ca9b7f5402fa3e436cab71. Checked 2026-09-24 01:46:27 UTC.
4ad2d377f7923ecd7728b9d1858020f27a58f5ea6e9c14e6a76d402c33ef2bcc
Both payments are on their chains and locked to the same secret hash 5f52e2128cabac9a8386bd06885894412472ad3e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4ad2d377f7923ecd7728b9d1858020f27a58f5ea6e9c14e6a76d402c33ef2bcc
- MakerPaymentSpent: 68530b595873a1dd36d34ad4470ccb3a5b04ba9b87ca9b7f5402fa3e436cab71
8c39c4bed62cfaaba30c0e50288723933125ff5100ccffbcc34516eebaaca29c
Both payments are on their chains and locked to the same secret hash 5f52e2128cabac9a8386bd06885894412472ad3e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: dd70277d28bc31a94a5e84c34983e19dec6d5cffb4bba1a2cf8f3564254ef340
- TakerPaymentSent · TakerPaymentReceived: 8c39c4bed62cfaaba30c0e50288723933125ff5100ccffbcc34516eebaaca29c
- TakerPaymentSpent: a211fd41fa99d35b30c92e0b49995c5a8373f331aa9c2cb61b1219003d4e8239
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.