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 1792632600 for transaction to be confirmed 1 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 c429d49296bbcd817d74253eb3ee7143d2146828af6c706b0f1e2ff8cd6340c6. Checked 2026-10-22 09:29:35 UTC.
247df279a276ef408de554973403ae529a158b876a03e04486691e959933bd00
Both payments are on their chains and locked to the same secret hash f3d609e12e8e15c92da34bfaf0db5f45b5b35187, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 247df279a276ef408de554973403ae529a158b876a03e04486691e959933bd00
634f8d961fe7ef144edf35a7b1c80c572385931e4293f30990bf83f1065b266a
Both payments are on their chains and locked to the same secret hash f3d609e12e8e15c92da34bfaf0db5f45b5b35187, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 25504fbf5158c7b1972efa5ac7cb70aa8e7fabefaedf6373623fb85de50afac0
- TakerPaymentReceived: 634f8d961fe7ef144edf35a7b1c80c572385931e4293f30990bf83f1065b266a
- TakerPaymentSpent: a54d21cd4532c88b9a304eb343ad9b971d914dc9080174712ab5c15853082bb3
Reported by kdf-statsdb.