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 1793915712 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 8b20b15b9180760dee3f6dfaeb226e6071a10a887185b54f9093758d4f95bac0. Checked 2026-11-05 22:24:16 UTC.
20ff6ec96947225bcfdaafa3544cbf1b1f7af0c09224d0161386fb89397be1f6
Both payments are on their chains and locked to the same secret hash ac1aecd5e44d98461e6550f382d3716e790561e1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 20ff6ec96947225bcfdaafa3544cbf1b1f7af0c09224d0161386fb89397be1f6
440763eff2a759f5379b72c9a1567d24a1455d8a9103cceac7efd500b5bf9de4
Both payments are on their chains and locked to the same secret hash ac1aecd5e44d98461e6550f382d3716e790561e1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 8b6b17ff22302f278d2704fe4297bb8e1ab0935be401fd7210b5280a313f58d6
- TakerPaymentReceived: 440763eff2a759f5379b72c9a1567d24a1455d8a9103cceac7efd500b5bf9de4
- TakerPaymentSpent: 3ee80e5de22338bc555009a42a68f1d0ed6154b0a969a6d842c461a11ea44f77
Reported by kdf-statsdb.