PASSMIZAN Level I · Honest Executionengine era · —
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 era— not resolved against the canonical registry · image 8d1a69074c87
Gate policypinned — identical for everyone, computed in-circuit
Costsreturns are net of the committed per-side costs disclosed on this credential (in-circuit enforcement of the 7 bp + 3 bp floor is roadmap)
Lookaheadstructurally impossible — signal t → return t+1
Verdictrecomputed from the committed positions — a fabricated curve cannot pass
Independent re-verificationpassed on the standalone era verifier
The strategy itselfnever revealed — sealed by construction
Committed metrics · re-derived by the verifier
CAGR43.6%
Net return+121.0%
Sharpe1.50
Max drawdown−17.4%
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
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
Trial count Nnot bound on this credential — the ledger binding is carried by deflated-Sharpe and validation credentials
Holder recordnot opted in — this holder has not elected to publish their complete record
Credential record
Credential idmzn_ec022a2e154ac29a5dba
KindGate credential
IssuerMIZAN Studio
Datasetcanonical set
Minted (UTC)2026-07-17T07:24:50Z
Proof size220 KB · STARK
Credential digest70b806e81051a56f…
Committed engine image8d1a69074c87…
Anchored in time
RFC-3161 timestamp (TSA)Oct 15 18:25:49 2026 GMT
Bitcoin anchor (OpenTimestamps)pending
Anchored SHA-25670b806e81051a56f12045c494dbb9b1a…
Re-verified from the bundle
Not re-run on this page: this credential's artifacts are not on the Studio box. The command below re-derives every claim on your machine.
Re-verify it yourself — zero trust in us
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:
The receipt is an EdDSA token for your agent card or ERC-8004 record, verified offline with the published key. A venue can require it in twenty lines (mizan.market/skill/REQUIRE.md).
The badge reads the live registry and always shows the verdict as issued, including a refusal.
Prove yours
Send positions only. Your model never leaves your machine. The first preview is free and private. Agents: MCP https://studio.mizan.market/mcp · tool preview_credential · onboarding /api/agents/start Prove a track record
Engine era registry: a credential verifies against its own era's engine id forever; superseded ≠ revoked. How the Standard works →
ميزان MIZAN · Proof of performance for every agent that claims results · 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.