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 MakerPaymentSpendFailed. The taker's claim on the maker's coin was rejected; it can be retried while the timelock holds.
taker_swap:2010] "eth:3092] request MethodCall(MethodCall { jsonrpc: Some(V2), method: "eth_sendRawTransaction", params: Array([String("0xf901088201368083014c0894edc5b89fe1f0382f9e4316069971d90a0951db3180b8a402ed292b652eb51c109ee05e1275b9c17083e7dc59b34c9d3b6178c15ba793c8b2c1d1370000000000000000000…
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.
142dd37a2ab6199620973a5c4a408f54e690ab422c01f09d6223d29e2318f305
Both payments are on their chains and locked to the same secret hash 860be1f80bf93fa08bb6abf0ff3a8f91abea8430, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 142dd37a2ab6199620973a5c4a408f54e690ab422c01f09d6223d29e2318f305
43c5947b4d3f421319e3c54b3f7cba7c3cafe5347fb04ce6cbdc7e9ffd668b14
Both payments are on their chains and locked to the same secret hash 860be1f80bf93fa08bb6abf0ff3a8f91abea8430, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 436655770ef005c7055e7b1ba7391662df0d39aa8376b921cd73792e1380c614
- TakerPaymentReceived · 43c5947b4d3f421319e3c54b3f7cba7c3cafe5347fb04ce6cbdc7e9ffd668b14
- TakerPaymentSpent · 67340bee1c80543bb28d442663771793fd2b67587ff14c9d27de6f777b81ea10
No anomalies were recorded against this swap.
Reported by defistats-gleec.