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 for as long as that payment is unspent.
taker_swap:2010] "eth:3092] request MethodCall(MethodCall { jsonrpc: Some(V2), method: "eth_sendRawTransaction", params: Array([String("0x02f9011082a4b18203c8808401ce1174830249f0949130b257d37a52e52f21054c4da3450c72f595ce80b8a402ed292b2df623e3ac303ca35dc15fcecd10b2d6aa1a63dd900f63e87f0bc29b93629e610…
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-10-01 19:30:08 UTC.
9732cb94860882564023c0c976dcfefa7fdf9d6f8799c7552e500133a05878c6
Both payments are on their chains and locked to the same secret hash 4bac5b09f2c4e0f46d44a9e0a33bfc03f79ce9e2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9732cb94860882564023c0c976dcfefa7fdf9d6f8799c7552e500133a05878c6
47d5a159ebb5bafeb40efd9f3726be6e8cebdb0e49de28e1155e70416d17c1f7
Both payments are on their chains and locked to the same secret hash 4bac5b09f2c4e0f46d44a9e0a33bfc03f79ce9e2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 029dc3dd230e18dcbdc85e82097cfb2f767462f4f59a0f25b22ae27f806f017c
- TakerPaymentSent · TakerPaymentReceived: 47d5a159ebb5bafeb40efd9f3726be6e8cebdb0e49de28e1155e70416d17c1f7
- TakerPaymentSpent: 1c411bf3a6a69ed8e5826b31fc3da444cd77ef38a5c366cd561efcb1a7a61ec5
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.