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("0x02f9010e82a4b10f8084016694e08302f9b8949130b257d37a52e52f21054c4da3450c72f595ce80b8a402ed292bb5f5b4aef778c7480f5b9601…
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:57:34 UTC.
c3066b25f9be307d82c57545c622693e6d38fca91c8ffe11bdf5088c27786be6
Both payments are on their chains and locked to the same secret hash 75723c51ebf7e78173e0001440ab9e981a2257a3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived: c3066b25f9be307d82c57545c622693e6d38fca91c8ffe11bdf5088c27786be6
- MakerPaymentSpent: 84c44a3128ab4b2ca2c1d475724376e251cd340e15dd07a0b8dd02060b3c2a4c
ffb82610dc670e92b4eef07c92f914eea0cc52f346b1a192e6c09f5e426e0779
Both payments are on their chains and locked to the same secret hash 75723c51ebf7e78173e0001440ab9e981a2257a3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent: 78bfddd9dfcbce1f96ab84f740fa5536807e2fb42c7635518b8314397f5babdd
- TakerPaymentSent: ffb82610dc670e92b4eef07c92f914eea0cc52f346b1a192e6c09f5e426e0779
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.