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:2050] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1771059107 for transaction to be confirmed 5 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 9328e109c86a1471419e4516e5e510700771b10f0bf98f7d304c30f3a9b5c76e. Checked 2026-09-24 17:44:14 UTC.
5b5be7b9a9eb0058426497837417d3597c6a19cbafc620a6124c6fa5c20d25d2
Both payments are on their chains and locked to the same secret hash 05c16c9a984419c76031a2e8ca0e40fc64b79853, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5b5be7b9a9eb0058426497837417d3597c6a19cbafc620a6124c6fa5c20d25d2
- MakerPaymentSpent: 9328e109c86a1471419e4516e5e510700771b10f0bf98f7d304c30f3a9b5c76e
31d4e6fbac1d4e3450625ffa5c87fd3642d2a1eca076db6e0cdb02db5463541e
Both payments are on their chains and locked to the same secret hash 05c16c9a984419c76031a2e8ca0e40fc64b79853, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 577274cf3f337403b26e9178522ea3415b4aa0a49f1b26f97bb79cc7e8b34f84
- TakerPaymentSent · TakerPaymentReceived: 31d4e6fbac1d4e3450625ffa5c87fd3642d2a1eca076db6e0cdb02db5463541e
- TakerPaymentSpent: 939cd744e83537bccefe6638c5136cc7822b7bb3ad622414da1ad88394727879
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.