Every agent claims results.
Now it can prove them.

MIZAN turns a trading agent’s record into a zero-knowledge proof: real after costs, out of sample, and counted against every strategy it tried. Allocators verify it in 81 milliseconds. The strategy never leaves the agent.Human-run strategies go through the same pipeline.

Works with Canonical market dataCommitted by hash Any agentHuman traders too · same gate Offline verifymacOS · Linux
Product overview

From a private agent to a public verdict, MIZAN covers the full proof lifecycle.

Outbound from your machineMONITORING
Strategy source and rules0 BSTAYS HOME
Model weights and prompts0 BSTAYS HOME
Features and signals0 BSTAYS HOME
Salted commitment0 BFINGERPRINT
Proof bundle0 KBLEAVES
Not recoverable from the credential · not by an allocator, not by MIZAN

Privacy

Your strategy and your IP stay yours.

The strategy is sealed behind a salted commitment, so only its fingerprint is ever public. Your code, rules, model and weights stay on your machine. What leaves is a proof and the metrics it certifies. Nothing in a credential can be turned back into the strategy. That is a numbered requirement of the standard, not a line in a privacy policy.

The same holds for human-run strategies. For models and black boxes, the sealed path submits only the positions the model took.

VTR-1 · R-09 · R-12
Credentials minted, by month— credentials

Prover

The agent's record is recomputed inside a zero-knowledge proof.

The agent's strategy runs against committed market data inside a zkVM on a pinned engine image. Returns and costs are recomputed in the proof, and the trial ledger is committed before evaluation, so every committed trial, including each model version you commit, counts against the one you show. The chart is the live wall.

VTR-1 · R-05 · R-06 · R-09
credentialhonest-fail-spy-sharadar
gateFAILSharpe ≥ 1.20 · 0.41
gatePASSMax DD ≤ 25% · 21.1%
evidence.json{ "verdict": "FAIL · SharpeTooLow · CagrTooLow · WalkForwardFailed",
  "dataset": "SPY daily 1997→2026",
  "published": true }

Gate

One fixed policy for every agent. Pass, or be refused in public.

The gate is pinned by the engine era, identical for every strategy, and cannot be chosen by the prover. This is a real refusal: our own S&P 500 trend engine, refused by our own gate over 28 years of survivorship-free data, and published anyway.

VTR-1 · R-37 · R-07 · R-11
Live · studio.mizan.market/api/registry

Registry

Every verdict, appended to one public root.

Passes and refusals land on the same append-only wall, committed to a single registry root. Nothing is removed and nothing is reordered. The list on the left is pulled live as this page loads.

VTR-1 · R-18 · R-40

Verifier

Anyone checks a credential offline, without trusting us.

A single binary re-derives the data root from your own copy of the data, checks the receipt against the pinned era image, confirms the registry leaf, and recomputes the statistics with exact equality.

VTR-1 · R-01 · R-10 · R-12 · R-13
How it works

A self-contained system for proving, and re-proving, a track record

Input
Committed datadata root · SHA-256
Trial ledgerevery attempt · before results
Strategyprivate · your machine
MIZAN engineRISC Zero zkVM · era v12
Output
Credential bundleSTARK receipt · ≈225 KB
Registry leafappend-only root
Verdictpass or refused · published
Ways to use it

MIZAN fits how you already work.

Hosted

Studio

Mint through the hosted studio. Minting is free during open testing; paid tiers begin when it closes.

Your machine

Offline verifier

Download one binary and check any credential on your own hardware. No account, no network, no trust in us.

Open

Registry API

Read every credential and refusal as JSON, with the registry root that commits to the whole set.

Give your agent
a proof.

Book a demo

Read the standard behind every proof

VTR-1: 41 numbered requirements, three conformance levels, and a verification procedure that never asks anyone to trust us.

Read the standard

Certify your agentor your own human-run strategy

Book a demo →