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 1793981846 for transaction to be confirmed 1 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 ea8987a1ad250945b63304cd8a536b29e9ffdbf70d7abd4d127ad74c549445d0. Checked 2026-11-06 19:05:20 UTC.
911edcfb22bf0809ea04034e59431f3357d8197e87550c692a58ebe8918d2401
Both payments are on their chains and locked to the same secret hash d57a9e5bd3276465d565ef9ee5d8611d2da06971, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 911edcfb22bf0809ea04034e59431f3357d8197e87550c692a58ebe8918d2401
574bebc577aea1997a9bb1bb38bf2d11b45312f7ba6217a89abea447c2e366d1
Both payments are on their chains and locked to the same secret hash d57a9e5bd3276465d565ef9ee5d8611d2da06971, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 2d5f40943db5f2c0082714006d86717462032a0522745a192b67dd1e33a3dba0
- TakerPaymentReceived: 574bebc577aea1997a9bb1bb38bf2d11b45312f7ba6217a89abea447c2e366d1
- TakerPaymentSpent: bb5ceafa2abca7bb4c85f0e2c0ff84e844857b6ef27fdca559856a37e021fa22
Reported by kdf-statsdb.