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 1789835107 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 be retried for as long as the timelock holds, and whether it was 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 31f57b063cb9669530e3544a87baeb966faa2efe7622d8427cde615a67dfdf2e. Checked 2026-09-22 12:35:27 UTC.
a3c2e9c572a31b42327b378d599019ae32eb5a26320ee8d3fde82a627946ff9c
Both payments are on their chains and locked to the same secret hash 2f5377b86655d4911a772be0d22599675aa4e757, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · a3c2e9c572a31b42327b378d599019ae32eb5a26320ee8d3fde82a627946ff9c
b40c3548adac318c05623bffaaf2901e4d12aa2e7bd78dd233414b8ed1fd5bea
Both payments are on their chains and locked to the same secret hash 2f5377b86655d4911a772be0d22599675aa4e757, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 07690a0fffff0bbe1ecb18df6f1711472cf8b1f687d9ea6da02b52bec46a67ad
- TakerPaymentReceived · b40c3548adac318c05623bffaaf2901e4d12aa2e7bd78dd233414b8ed1fd5bea
- TakerPaymentSpent · 85c97da8688ddfa3da846e04d213c4b665fcc04e4a69b03c2d6a26720a3c11b8
Reported by kdf-statsdb.