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 TakerPaymentSpendConfirmFailed. The maker's claim on the taker's coin was broadcast but not seen to confirm.
maker_swap:1322] !wait for taker payment spend confirmations: rpc_clients:119] Waited too long until 1755147983 for transaction to be confirmed 7 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 be retried for as long as the payment is unspent, and until the timelock passes nobody else can touch 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 351e64aac85e2774a7d5543f0ddb25ab4da04dfb81d66aa9b3f75815ede14160. Checked 2026-09-24 19:04:12 UTC.
a6bdf7cec2dfb92cc0d6ea97290dafe29f1f0b70ce91902009f727c2caa1a99a
Both payments are on their chains and locked to the same secret hash c0eca6e7dfabf4eff436f5bb516554df0cbf0edc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a6bdf7cec2dfb92cc0d6ea97290dafe29f1f0b70ce91902009f727c2caa1a99a
- MakerPaymentSpent: 7014f58c498447dd6cf5a9771ba17a25fdf1ae22955b45979c6d969611b745ee
42b91ee88e3b3d384e5fb523b5c2730adfafbb1a06d411a77b73434f4b69b6ab
Both payments are on their chains and locked to the same secret hash c0eca6e7dfabf4eff436f5bb516554df0cbf0edc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: d6ca3371da9d818616155a9860b228124356555567c5c73ff992f956c1587941
- TakerPaymentReceived · TakerPaymentSent: 42b91ee88e3b3d384e5fb523b5c2730adfafbb1a06d411a77b73434f4b69b6ab
- TakerPaymentSpent: 351e64aac85e2774a7d5543f0ddb25ab4da04dfb81d66aa9b3f75815ede14160
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.