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 1755148122 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 964cf9b9bca2059cc831f618829d2def068806df1e49c18e4e8e05a8d65c1638. Checked 2026-09-24 19:04:14 UTC.
0ee20593316594f995b55be17ce2b2e2eba87bfc56908a423ce7183516cc2072
Both payments are on their chains and locked to the same secret hash 76c20369d3ed0eb4c5313bdd86463c3f07db569e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0ee20593316594f995b55be17ce2b2e2eba87bfc56908a423ce7183516cc2072
- MakerPaymentSpent: d3c9f0dab0fe53e72b287c7b680b54f0df8e1cccf783b3113a112dbcabb07b94
dd7d3be4604f968902f353f98b4d0ba345c15a17a16dccf843e83917f4888602
Both payments are on their chains and locked to the same secret hash 76c20369d3ed0eb4c5313bdd86463c3f07db569e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: cd91b66ec961be52028175032d1515d6680a859af8caa441ec23b471dc8075b7
- TakerPaymentReceived · TakerPaymentSent: dd7d3be4604f968902f353f98b4d0ba345c15a17a16dccf843e83917f4888602
- TakerPaymentSpent: 964cf9b9bca2059cc831f618829d2def068806df1e49c18e4e8e05a8d65c1638
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.