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 1793802834 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 36e22b70cde33db4d1a385b0bc6637ca9c4d1c60d07a123ce561c2a8d5783356. Checked 2026-11-04 19:53:45 UTC.
45218b871114a4978320162794776e45df25898cae67b34c64e032598372278e
Both payments are on their chains and locked to the same secret hash 26e28df5840cb03be0abb47eb830821b1d335134, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 45218b871114a4978320162794776e45df25898cae67b34c64e032598372278e
f08b396356e435799e68a47c876d08181755e2ab4ef746973c686d7d13d137b4
Both payments are on their chains and locked to the same secret hash 26e28df5840cb03be0abb47eb830821b1d335134, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 8c3781f92fd0181c36f1bbc8c54833520e9f263ff61db57dafbaef8e15fb2276
- TakerPaymentReceived: f08b396356e435799e68a47c876d08181755e2ab4ef746973c686d7d13d137b4
- TakerPaymentSpent: 6ec75f8dfbcedf355635dfafdfe6b6c32e7f4f86ee6a4e9c7cc86420b3a323d9
Reported by kdf-statsdb.