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 TakerPaymentSpendFailed. The maker's claim on the taker's coin was rejected; it can be retried for as long as that payment is unspent.
maker_swap:1269] !taker_coin.send_maker_spends_taker_payment: "eth:3268] request MethodCall(MethodCall { jsonrpc: Some(V2), method: "eth_sendRawTransaction", params: Array([String("0x02f9010e82a4b1068084016694e08302f9b8949130b257d37a52e52f21054c4da3450c72f595ce80b8a402ed292ba386ba6c9fd633b3536184ff…
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-11-11 02:47:34 UTC.
800d22f3371ff3c2866e45637b0355f3532fe96221018b46ea0b1fe7d3246a2e
Both payments are on their chains and locked to the same secret hash 6d8a9c2456a12b32c0c3fdac56deab930f3cb1c3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived: 800d22f3371ff3c2866e45637b0355f3532fe96221018b46ea0b1fe7d3246a2e
- MakerPaymentSpent: fc31ff57271e8b5bfbcbc30dca4237acb14faf04ba71ae90407155cd32ba8719
89c56905c3f1bbb5947de2c69451b6d36df130def7938c70c7c6639055ebd1d2
Both payments are on their chains and locked to the same secret hash 6d8a9c2456a12b32c0c3fdac56deab930f3cb1c3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent: 6e7aa270cf58d12d7dc3ab5c9d92e2cdfd8101311219c1d2bc2425196b75e436
- TakerPaymentSent: 89c56905c3f1bbb5947de2c69451b6d36df130def7938c70c7c6639055ebd1d2
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.