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:1909] !wait for maker payment spend confirmations: rpc_clients:112] Waited too long until 1766202963 for transaction to be confirmed 10 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 beff8b2b2135c8881cc0684263a28e0ca54bd659e8354fd76ae23e72c0e6d55a. Checked 2026-09-24 18:24:12 UTC.
d6aea585ecc00f0298c27ee176d51c9e270628d1d9132dc890e7a2c5e63072f5
Both payments are on their chains and locked to the same secret hash f67fed29195d5963d82954ae118e232ace56b773, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d6aea585ecc00f0298c27ee176d51c9e270628d1d9132dc890e7a2c5e63072f5
- MakerPaymentSpent: beff8b2b2135c8881cc0684263a28e0ca54bd659e8354fd76ae23e72c0e6d55a
1e87e73642a78d0fea68385d0cfc15763cc0807cd1bcf58db3f32ddc20a9d140
Both payments are on their chains and locked to the same secret hash f67fed29195d5963d82954ae118e232ace56b773, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 47213d46b2fd026985b4782e44c9576c2b7691df7c7c53d2a5abb5585adbe016
- TakerPaymentSent · TakerPaymentReceived: 1e87e73642a78d0fea68385d0cfc15763cc0807cd1bcf58db3f32ddc20a9d140
- TakerPaymentSpent: 8dbc079fa332dc466998855c23acd33a9f9a2d8f2b2f713eddb54215ce9f0ec1
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.