check(1): checking a batch and contesting

How to find out where your order went, and what to do if the room flagged it.

Check a batch

Open any batch from the log. The page reads the commitments, the prices and the outcome of each slot from the chain, and verifies the proof in your browser. A verified proof means every slot was treated by the rule.

Check your order

$ check zkdp-order-5971204-0x1a2b3c.json
commitment   matches the file
slot         3 in batch 5,971,204
outcome      unmatched: your limit $238.00 did not cross $241.37
published    nothing

On check, open your order file. The page confirms the file hashes to its commitment, finds the slot, and explains the outcome: matched (with the fill), unmatched (and why: your limit did not cross, or the other side did not cross), void, expired, or flagged.

Contest

If the room flagged your slot as broken while your order file is the one you sealed, press contest. contest(batchId, slot, inner) checks onchain that your inner ciphertext hashes to the slot's commitment and records a permanent Excluded event. Whether the time-locked layer you posted held that ciphertext is public: anyone can open it with the round's beacon and compare, which the batch page does with "check the flag". The stats page counts proven exclusions; the target is zero.

/ search · [ ] previous and next page