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 1785956871 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 d5d5dd08a68af796ca152c832eba4833e25c56280cb302749b447fe021f116fb. Checked 2026-09-24 01:56:11 UTC.
a541918dbee04561f767798da1e7f99271276f4bf0b7e6d477d48653086a626f
Both payments are on their chains and locked to the same secret hash 6f5afbbb06472a9f614d14cc2d77b2f9dc41009e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a541918dbee04561f767798da1e7f99271276f4bf0b7e6d477d48653086a626f
- MakerPaymentSpent: d5d5dd08a68af796ca152c832eba4833e25c56280cb302749b447fe021f116fb
8ab578fccd7c6edb88d930a6a233c68a4471ed0abf97e2bdc7bdee9574dcef4a
Both payments are on their chains and locked to the same secret hash 6f5afbbb06472a9f614d14cc2d77b2f9dc41009e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 27169ff81b3eb83bed12ef16204e40a5abc084d1e41032ebe17758c9400b3dd5
- TakerPaymentSent · TakerPaymentReceived: 8ab578fccd7c6edb88d930a6a233c68a4471ed0abf97e2bdc7bdee9574dcef4a
- TakerPaymentSpent: d9dafb5a7babbec17252a0e04f19efa1b3f2c461194bce0cc21d85f9d527966a
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.