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 474fc3fa05d400fc1067012eae6a96f0eb8bbf2cd7868f7efa61d14afb8c9130. Checked 2026-10-26 23:20:30 UTC.
1ecad03aa2e0f7174385b969a66301635cd1f4c7c0532c83922eaf9364b251b4
Both payments are on their chains and locked to the same secret hash 8fe31a47a09d382fc4a422ae056519b283c057e9, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1ecad03aa2e0f7174385b969a66301635cd1f4c7c0532c83922eaf9364b251b4
8695d8262d212d74216145a99d38452252b85d2eb8cf97b3bd6e02e951d6b633
Both payments are on their chains and locked to the same secret hash 8fe31a47a09d382fc4a422ae056519b283c057e9, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0f0ef039d83125c3e31441bd7a145ed7ca8344328bd828c52dfabff91174de2e
- TakerPaymentSent · TakerPaymentReceived: 8695d8262d212d74216145a99d38452252b85d2eb8cf97b3bd6e02e951d6b633
- TakerPaymentSpent: 29efb1dc27713410d02f2e649d70270a02b895463f07e293f3aaf8bf3c30d175
Reported by kdf-statsdb-8762.