A cryptographic credential on the MIZAN registry — every number below is committed
inside a zero-knowledge proof and re-derived by an independent verifier. The strategy itself is
never revealed.
STARK sealverified — no trusted setup, re-checkable by anyone
Committed journalbound to this credential — one changed byte and every verifier rejects it
Engine erarecognized — v11 · image 3ac3b10b7930 (append-only era registry)
Labels in-circuittriple-barrier + meta-labels + uniqueness recomputed from committed bars
Parameter-bound digestsrelabel-by-redeclare is impossible
Independent re-verificationpassed on the standalone era verifier
The strategy itselfnever revealed — sealed by construction
Committed metrics · re-derived by the verifier
Events committed8 · over 1096 bars
Barriers · pt / sl200 / 100 bps
Vertical horizon12 bars
Meta-label act rate0.2500
Labels digestc150c662f0ee8bc0…
Uniqueness digest843a1ee13d2212b2…
What this proves · what it does not
Provesthe committed computation ran on the pinned data under the locked gate — net of the committed, disclosed costs, with the committed trial ledger
Does not provefuture returns · deployable capacity · real-world fills beyond the committed cost model · transfer to other assets or windows · robustness to search multiplicity — a separate credential class, and one our own flagship fails
The verdict on this page is not an assertion by MIZAN — it is recomputed on
your machine from the proof bundle. Download the bundle, grab the pinned era verifier and
the canonical dataset from the Verify page, and run:
Minted by engine era v11 — append-only era registry: a credential verifies against its own era's engine id forever; superseded ≠ revoked. How the Standard works →
ميزان MIZAN — the verification rail for systematic finance · Mizan Verification, Inc.
Every claim on this page is re-derivable from the proof bundle by anyone, trusting no one — including us. Prove the edge. Never reveal the strategy.