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.
the transaction was rejected by network rules. mandatory-script-verify-flag-failed (Signature must be zero for failed CHECK(MULTI)SIG operation) (code 16)
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 payment was spent with the preimage, in b104b8be23776c8c317ffbe3f4ac1bfdf5ed473216aef89a1a451225f21a4962. Checked 2026-10-26 15:00:21 UTC.
1698a208ae9cba2517c414575fdb76e6529b66d1c2ff33d0ff47b2aacf09b074
Both payments are on their chains and locked to the same secret hash 36734faa8c64838275ac4878863b074eda23a548, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1698a208ae9cba2517c414575fdb76e6529b66d1c2ff33d0ff47b2aacf09b074
7dd10b46b031903f3df17fb494f32d594d2e0cb7d526de548cceba2a81b23f66
Both payments are on their chains and locked to the same secret hash 36734faa8c64838275ac4878863b074eda23a548, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2ca7d62a6770adefe0879fb83b413b454df3f631cf94116336146f31878813ab
- TakerPaymentSent · TakerPaymentReceived: 7dd10b46b031903f3df17fb494f32d594d2e0cb7d526de548cceba2a81b23f66
- TakerPaymentSpent: 10f4e8693557671c9f366c0cca06f5d3790b51928029ed289fab3ed65b84b9fb
Reported by kdf-statsdb-8762.