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 while the timelock holds.
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 be retried for as long as the timelock holds, and whether it was is a question for the chain rather than for this log.
The chain shows the maker's payment still sitting in its contract: neither claimed nor refunded. The maker had already collected the taker's payment by this step, so the taker paid and has not received the maker's coin; the maker can take it back after the timelock. Checked 2026-09-22 15:46:16 UTC. It will be asked again.
72c88d7cba177d1b7afda0fd67147f199d2d38f68d1a21a7d43a6ca2edc71e3b
Both payments are on their chains and locked to the same secret hash b710005b52789a20d500c2df78d80aa22d2f14f0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 72c88d7cba177d1b7afda0fd67147f199d2d38f68d1a21a7d43a6ca2edc71e3b
8161a0e8723b6c72a5e6bb7f5c569706a382e097bad9073d7cbf6d3d3cf975de
Both payments are on their chains and locked to the same secret hash b710005b52789a20d500c2df78d80aa22d2f14f0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 5b4fe0af9694ee1112ed3d4f4f469e733895461f71f4330286d9f25773cbccee
- TakerPaymentReceived · 8161a0e8723b6c72a5e6bb7f5c569706a382e097bad9073d7cbf6d3d3cf975de
- TakerPaymentSpent · 16074a14287d696b086e09cfc0efbe4942e3aae96b22807d0e184194ddb878ec
Reported by defistats-gleec.