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 1791495093 for transaction to be confirmed 7 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 a5366e7375307ee3bcfd64bf98480301dd589dfa050e65b96ac3e6f7c6c15356. Checked 2026-10-09 16:15:20 UTC.
d52125495e0afc5797b544a790a65e2ef623d113885d9f0509f6f9f1a6e0f116
Both payments are on their chains and locked to the same secret hash 12390d87d8e73206355939f359fc40201afd1ec1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: d52125495e0afc5797b544a790a65e2ef623d113885d9f0509f6f9f1a6e0f116
b97773850d52bce957cd5b61bed63de7979571acc4e4dadf57de3b71c99ecd1f
Both payments are on their chains and locked to the same secret hash 12390d87d8e73206355939f359fc40201afd1ec1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 791d8db04c93eb78e9dc89b418e29912b076c4906e83c31b3c575ce37a7b5992
- TakerPaymentReceived: b97773850d52bce957cd5b61bed63de7979571acc4e4dadf57de3b71c99ecd1f
- TakerPaymentSpent: 706ad7c00e61a67e2741566f7a5fb7b876e9b5d0a431c3811c14ad8cbfffe858
Reported by kdf-statsdb.