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 1793218505 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 09fa0ed53810e5bdc55d0daa06d331758981def9364518bd94b3b1b448089694. Checked 2026-10-29 17:31:35 UTC.
2f9b5744eac1f7cf109049daf346fe4cb4c8f5820a10215bfee2021e3abb3cf1
Both payments are on their chains and locked to the same secret hash 733690bde92ba1383804e00cba243b0145af5cae, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 2f9b5744eac1f7cf109049daf346fe4cb4c8f5820a10215bfee2021e3abb3cf1
9cc051268f5c0394dad1371282b39a4b6c1743d70e692470f3b7229f006eb121
Both payments are on their chains and locked to the same secret hash 733690bde92ba1383804e00cba243b0145af5cae, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: d24bb4cc4e0f6f85992f0a845e0668805bd55093016b0aca7eb9be049ba7046d
- TakerPaymentReceived: 9cc051268f5c0394dad1371282b39a4b6c1743d70e692470f3b7229f006eb121
- TakerPaymentSpent: a3f6f95216b7e2cbaed7cc0918673319acd034fc006785ba69bf0cec8904b5cc
Reported by kdf-statsdb.