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 1793362013 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 03900afa9a6c3f641d058466210c4e87b300471cbafc43e5e52b96dbf3bc5471. Checked 2026-10-31 10:52:07 UTC.
6522c5e988ebf3878dc9cb1ac7593e5bde11a85483cb045f64bf5b38a31b7a5d
Both payments are on their chains and locked to the same secret hash a0643136d2957ba01c1786d83ae60ec078936624, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 6522c5e988ebf3878dc9cb1ac7593e5bde11a85483cb045f64bf5b38a31b7a5d
060a7ed3a6abd476bcba5595de596574d8b2cbd6df31f5d6e4ddb77ac6c3ea29
Both payments are on their chains and locked to the same secret hash a0643136d2957ba01c1786d83ae60ec078936624, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 45b2987f442aa01bef53e16c9e9e54066ff2bb6a48a4d6d25a5ab5db46d28252
- TakerPaymentReceived: 060a7ed3a6abd476bcba5595de596574d8b2cbd6df31f5d6e4ddb77ac6c3ea29
- TakerPaymentSpent: ff0008fe2443aa7ad6a9e00833e4340fd475927e06c7be5a5d23ed1d8857e40e
Reported by kdf-statsdb.