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:2892] request MethodCall(MethodCall { jsonrpc: Some(V2), method: "eth_sendRawTransaction", params: Array([String("0x02f901108221050e830f42408312f2d2830249f0944c54808911817402a0871c3c93d8790c19cae75b80b8a402ed292b6e543da7f9fd64c6a82d…
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-09-24 18:24:17 UTC.
c6c4ed04f286f077d1de801d173dbd051c3c5fcd1feff8bd066f40c7b68b39af
Both payments are on their chains and locked to the same secret hash a1e6ba197a8ddbc81aa0b8f4861a105b8c26ae1d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c6c4ed04f286f077d1de801d173dbd051c3c5fcd1feff8bd066f40c7b68b39af
- MakerPaymentSpent: 693ef37421e1d1f68e33da2643a39d4058aed563d6be5adfd93327b9c2698658
c0a9d5964011ba8589e817ca6bbcd92e72652b23b62845332f3fb6a1ab214feb
Both payments are on their chains and locked to the same secret hash a1e6ba197a8ddbc81aa0b8f4861a105b8c26ae1d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5d486813330b21bc55b38b6aa99b3dee989e4c4281d1c6b47158f7f825666101
- TakerPaymentSent · TakerPaymentReceived: c0a9d5964011ba8589e817ca6bbcd92e72652b23b62845332f3fb6a1ab214feb
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-8762.