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:2044] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1762369677 for transaction to be confirmed 1 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 3be7587fa7468c79394c596111ffdc19917e6ae50e70c526fca640b4b2c082d8. Checked 2026-09-24 18:44:15 UTC.
e3dec27be3210f17691daed8cdf122295b6b3def2c710763f3ad80f2e473d34f
Both payments are on their chains and locked to the same secret hash 234edd65bfadbe346977bf6b3a85633199791c6b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e3dec27be3210f17691daed8cdf122295b6b3def2c710763f3ad80f2e473d34f
- MakerPaymentSpent: 3be7587fa7468c79394c596111ffdc19917e6ae50e70c526fca640b4b2c082d8
c9131e64fae1d801e2e97dc27b118528b0ff2a69e4c47666400aca23100ced25
Both payments are on their chains and locked to the same secret hash 234edd65bfadbe346977bf6b3a85633199791c6b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3db94ae1186437c0f0571ffebbe59493c40fa07037dc9929b189a913ff520e61
- TakerPaymentSent · TakerPaymentReceived: c9131e64fae1d801e2e97dc27b118528b0ff2a69e4c47666400aca23100ced25
- TakerPaymentSpent: 2de762125c094f3912f4f237ef3c1f28fa70c890cd4860b99f6c01902ec3401c
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.