PASS ✓ — Sharpe≥1.20 · CAGR≥20% · MDD≤25% · all in-circuitMIZAN Level I · Honest Executionengine era · v11 · both-schools validation-complete
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)
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.41 / 0.84
CAGR23.0% (net +542% · 8.9y)
Max drawdown · worst bar−18.7% · -8.5%
Calmar · exposure1.24 · 27.8%
Trades125 (5442 of 19585 bars)
Independence (1−R²)57% · mkt 20% mom 41% rev 4%
Costs in-circuit7+3 bps
Out-of-sample flag. OOS Sharpe 0.84 — below the 1.20 gate bar on its own; the composite gate passed.
Tuning disclosure. This configuration is the winner of an earlier BTC-specific research search, pre-registered before minting — the pass is in-domain evidence carrying its own search history.
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 idpass-btc-trend-4h
KindGate credential
IssuerMIZAN
DatasetBTC/USDT · 4h OHLC full history · 2017-08-17→2026-07-27 (19,585 bars)
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
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 · 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.
