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 1793390733 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 65fb852f4a4dd80c9d0753321eb9b23d5ac1d24919c676c8420d2cf38524aef1. Checked 2026-10-31 17:02:22 UTC.
02bf567b3e648f66f0a94f3328d1042a654c3658fe0255ce46b0c1232d55d973
Both payments are on their chains and locked to the same secret hash 0e1e46a1b95d99309f884869c00f8f052242c4bc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 02bf567b3e648f66f0a94f3328d1042a654c3658fe0255ce46b0c1232d55d973
f7613c700f7fb6acb739481a77402dd7e4e158a4c8ef86dc7ed2e0c32aefcbe2
Both payments are on their chains and locked to the same secret hash 0e1e46a1b95d99309f884869c00f8f052242c4bc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 54743597f01a76abb25162238b606196e305eda3f12f161a931dc665d8110229
- TakerPaymentReceived: f7613c700f7fb6acb739481a77402dd7e4e158a4c8ef86dc7ed2e0c32aefcbe2
- TakerPaymentSpent: 48dbb16fd4cfd5bb1122c89513be0b7894a67fbdebc39c1dc6dee43fd9fcb2af
Reported by kdf-statsdb.