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 1794411538 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 21ee1677e1ec217ac2eee4c42368dffc52fc9d5183ce22496eaa781b3de44280. Checked 2026-11-11 17:58:04 UTC.
b76f45f681c783671627f2b250a8f223ecf08d34e04f6630200f95943e462c30
Both payments are on their chains and locked to the same secret hash a75c8ffb6714d067e280fc85c43eb862ae3d5041, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: b76f45f681c783671627f2b250a8f223ecf08d34e04f6630200f95943e462c30
4dd50205ed36064f3ab13d4e3bd2ccaf73b248329ed34e3297a358b3b6fe93ee
Both payments are on their chains and locked to the same secret hash a75c8ffb6714d067e280fc85c43eb862ae3d5041, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 8fa8e2981cc2429cf953227f00ab4737b123bc609e02c960ace4b322c9cf2265
- TakerPaymentReceived: 4dd50205ed36064f3ab13d4e3bd2ccaf73b248329ed34e3297a358b3b6fe93ee
- TakerPaymentSpent: 9f6cfe97b7c45081aa0c21b5ade91fe26167967fcbbe6f0ae6685f655b3c115a
Reported by kdf-statsdb.