PASSMIZAN Level I · Honest Executionengine era · v10 · composed PBO S=16, n_eff DSR, fractional sizing
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 — v10 · image dafad185fe3e (append-only era registry)
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
Sharpe · full / OOS1.40 / 1.85
CAGR28.5% (net +112% · 3.0y)
Max drawdown · worst bar−20.3% · -9.3%
Calmar · exposure1.40 · 8.5%
Trades29 (93 of 1096 bars)
Independence (1−R²)82% · mkt 9% mom 12% rev 0%
Costs in-circuit7+3 bps
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 idbb-16349103c4d4
KindSealed-model credential
IssuerMIZAN Studio · self-serve sealed mint
Datasetbtc_daily
Minted (UTC)2026-07-23T02:06:39Z
Proof size220 KB · STARK
Credential digest166a2596cff8d43a…
Committed engine imagedafad185fe3e…
Anchored in time
RFC-3161 timestamp (TSA)Oct 15 18:25:35 2026 GMT
Bitcoin anchor (OpenTimestamps)pending
Anchored SHA-256166a2596cff8d43a361821b5b15c519d…
Re-verified from the bundle · studio self-serve job
This block is produced by running the published era verifier on the stored bundle and the catalogue series each time the cache expires — the page is rendered from the proof, not from a template.
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
Minted by engine era v10 — append-only 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.
