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:6103] Timeout: eth:6103] Waited too long until 1783685360 for payment tx:, for coin:BNB, 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 be retried for as long as the timelock holds, and whether it was 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-09-22 15:40:30 UTC.
e74da6826f8e91f00c15e24e23ace1c6af6289d89397b8bef7cc77a3edbe81b7
Both payments are on their chains and locked to the same secret hash 608aabe5773b27818a62355a59e7a91e06c311e4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · e74da6826f8e91f00c15e24e23ace1c6af6289d89397b8bef7cc77a3edbe81b7
e1e9a748b642ece83d803afb5b7547a07390419e2299fdb09f8fac82c65d1cb9
Both payments are on their chains and locked to the same secret hash 608aabe5773b27818a62355a59e7a91e06c311e4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 53f0d588be1a4c5c816f2f9f98430d94a6087fff31369c9e68804b418b025aa8
- TakerPaymentReceived · e1e9a748b642ece83d803afb5b7547a07390419e2299fdb09f8fac82c65d1cb9
- TakerPaymentSpent · 3f256d283615f0dddfaa8e7accb564cb02870e5dac270bf8c17086ab30671761
No anomalies were recorded against this swap.
Reported by defistats-gleec.