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("0x02f9011082210510830b47e9830ef331830249f0944c54808911817402a0871c3c93d8790c19cae75b80b8a402ed292b78c90dd23fe4a92ea7fb…
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.
f89d4f8f2d1fa9415ccdfe9656b32cc4e1df0a2ccfc5ba7cb021d2d356f5467c
Both payments are on their chains and locked to the same secret hash 2f63dcdb1f64cda657873f8d9925e9ca7d51bb9e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f89d4f8f2d1fa9415ccdfe9656b32cc4e1df0a2ccfc5ba7cb021d2d356f5467c
- MakerPaymentSpent: ef521b9fe4f66bb46d7182c06878f2af2348068d6c060e166b08b0364eb088e7
0326d2f8ef236547d4a1d7376b73238f96d6135ad813fce16dcfa0dd41c02141
Both payments are on their chains and locked to the same secret hash 2f63dcdb1f64cda657873f8d9925e9ca7d51bb9e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9d64cb3cc5d8f6ec17741a4fd4bfe1aa8b943301922e4a95380b4158d9815c36
- TakerPaymentReceived · TakerPaymentSent: 0326d2f8ef236547d4a1d7376b73238f96d6135ad813fce16dcfa0dd41c02141
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.