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 1791484624 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 4001f027e927be2581ca22c33faf41443dfb33f59ed96fe9901ecf414baa7a6f. Checked 2026-10-08 22:15:18 UTC.
daec84c77048ac4383aeab3f1a3ba6f610815321724d40c201226fe4d1782ecd
Both payments are on their chains and locked to the same secret hash 12fe0528ccd41f29cda93e7c41e7c73299ba6cfb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: daec84c77048ac4383aeab3f1a3ba6f610815321724d40c201226fe4d1782ecd
8b646314bbe52456f83672dc7f499f1f3e106d17f334de08960fd9f8c5226556
Both payments are on their chains and locked to the same secret hash 12fe0528ccd41f29cda93e7c41e7c73299ba6cfb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: fcb79f8788bda5eecc2ad2e8484eb8c6c0ce473c74556bec5e1c8bd1e4dada9a
- TakerPaymentReceived: 8b646314bbe52456f83672dc7f499f1f3e106d17f334de08960fd9f8c5226556
- TakerPaymentSpent: d6dbbb83300c103c0cb91c116ba3f0760f9f9f44e4a6928e6c2e0827705ada3d
Reported by kdf-statsdb.