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 1755147932 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 62763a75b911397871f2c89394b254a118a5d19bbec31dcedecdfc69a6d60f20. Checked 2026-09-24 19:04:14 UTC.
4e568adc1ff6fe01fafb0085cc631b2e8f25e31cc8db73faee19c1f67a5c1035
Both payments are on their chains and locked to the same secret hash 112409aa5508f9b13b844cabfff228fa097432e9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4e568adc1ff6fe01fafb0085cc631b2e8f25e31cc8db73faee19c1f67a5c1035
- MakerPaymentSpent: 95bc5e3d9fbf63ca64c09e4776d11a018cbe4a2f5390d9a1b556bbe5d81a707b
353e7be1c81af033857b407b1645c1f273df4c1924eb30855327a19df8b813d6
Both payments are on their chains and locked to the same secret hash 112409aa5508f9b13b844cabfff228fa097432e9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e1b44e51f3f230f1c92c575e7971cc41bcde687c29c8baafdb1ce4c0ef8b275c
- TakerPaymentReceived · TakerPaymentSent: 353e7be1c81af033857b407b1645c1f273df4c1924eb30855327a19df8b813d6
- TakerPaymentSpent: 62763a75b911397871f2c89394b254a118a5d19bbec31dcedecdfc69a6d60f20
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.