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:2052] !wait for maker payment spend confirmations: eth:6110] Timeout: eth:6110] Waited too long until 1792618893 for payment tx:, for coin:USDC-BEP20, to be confirmed!
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 swap contract records the payment as spent by the receiver. Checked 2026-10-22 04:19:29 UTC.
fff4526938cfd9e602f1adc069d4c0e56f341d581bf1bb69c18ef1f2b77b7f5e
Both payments are on their chains and locked to the same secret hash 94c3d227fbe6409f173ac48783d66daad85723b8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: fff4526938cfd9e602f1adc069d4c0e56f341d581bf1bb69c18ef1f2b77b7f5e
1c09735cdd4cc6bed5df1196a9e7c475b265ff17fdfe794561cfa35d0c54ce4f
Both payments are on their chains and locked to the same secret hash 94c3d227fbe6409f173ac48783d66daad85723b8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 8784358fc4018ba55ed231d956abe8bdb7c91020815901fc1ebbba7b161c62f8
- TakerPaymentReceived: 1c09735cdd4cc6bed5df1196a9e7c475b265ff17fdfe794561cfa35d0c54ce4f
- TakerPaymentSpent: 652ed2eb05a9a1cfc02b451989f0decc40e63ee3401f1e942b43fa5bbc5af2f4
Reported by kdf-statsdb.