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:1813] "eth:2551] request MethodCall(MethodCall { jsonrpc: Some(V2), method: "eth_sendRawTransaction", params: Array([String("0xf9010c1a843cf82f5083030d40949130b257d37a52e52f21054c4da3450c72f595ce80b8a402ed292b911515396ba6a70504c77249a2e8dae2ff9c6ef867ac3ef1fe93dbb1a4f45200000000000000000…
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 be retried for as long as the payment is unspent, and until the timelock passes nobody else can touch 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-25 21:53:13 UTC.
e4f93de658ce4e7b7d656bce53caf9014060ce2dda903a14c48cbb8babd31d04
Both payments are on their chains and locked to the same secret hash 714aaaeab1b99448f109cb62d083d4d706ee0688, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: e4f93de658ce4e7b7d656bce53caf9014060ce2dda903a14c48cbb8babd31d04
bf261976f2657b6861eabfd0cb5722986078bd044369b7247edd0410df823d81
Both payments are on their chains and locked to the same secret hash 714aaaeab1b99448f109cb62d083d4d706ee0688, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b639476f89b9a8e2fb556a7f6a14628adc14c5ed2841b07d5a4d0ca21813390c
- TakerPaymentSent · TakerPaymentReceived: bf261976f2657b6861eabfd0cb5722986078bd044369b7247edd0410df823d81
- TakerPaymentSpent: 5e23b7d82bc9e38c28530a5b3faa1633b559a7dc76fa2eb59ab61f926102cad7
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.