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 1793798075 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 110d70ba689868f0d4f423ca001da2aa1b2f6cc8c003fe8f13b5489252565b3d. Checked 2026-11-04 19:23:40 UTC.
337848ff91121e468dc64b685e982ac55d20d1da887777e29ef92bb2599fc210
Both payments are on their chains and locked to the same secret hash 5f1e2fa3e209bfed87a4cf89beaf4d36ad108958, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 337848ff91121e468dc64b685e982ac55d20d1da887777e29ef92bb2599fc210
4c353d347d01512c095d29f6a5709bf08aa5127de4ee372ff2faebc36d6f5c33
Both payments are on their chains and locked to the same secret hash 5f1e2fa3e209bfed87a4cf89beaf4d36ad108958, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 0162c401b9cf431a66c903b2fc56869f9e66fd7e2a397831d7227e06fe42c0fc
- TakerPaymentReceived: 4c353d347d01512c095d29f6a5709bf08aa5127de4ee372ff2faebc36d6f5c33
- TakerPaymentSpent: 7ac98094b2c4db220bbcd84098fa7a7283efffe7b9c95fb5a5b343d4d4b546f0
Reported by kdf-statsdb.