ميزانMIZAN
For platforms · integration
The verification layer
you don't have to build.
Your platform already computes honest statistics. The problem was never fraud — it is that a record earned inside your walls means nothing outside them, and a provider arriving from outside starts at zero no matter what they did before. MIZAN turns both into artifacts: portable, cryptographically verifiable credentials checked against an open standard, not against your servers or ours.
BrokersProp & funded-trader firmsCopy / social trading
TAMPs & model marketplacesStrategy marketplacesData & tooling vendors
Fund administrators
What integrating actually gives you.
Records that survive leaving your platform.today: a rank means nothing elsewhere
Your traders' verified history becomes an artifact they own and can show anywhere — which, counter-intuitively, makes them stay: you are where the proof was minted, and the credential names the venue.
Supply from outside your walls.today: every new provider starts at zero
Accept pre-verified providers from anywhere. A quant who proved five years of honest backtests elsewhere can arrive with that record intact, instead of spending a year rebuilding it inside your product.
A due-diligence layer you neither build nor defend.today: you vouch, so you carry the risk
Institution-grade statistics — deflated Sharpe against a committed trial count, probability of backtest overfitting, purged cross-validation, costs charged in-circuit — computed by a locked gate you don't operate. When a listing disappoints, the standard answered, not your brand.
A differentiator competitors can't copy by announcement.today: everyone claims "verified"
"Verified by an open standard, checkable offline by anyone" is a claim a rival cannot match with a marketing page — they'd have to adopt the same standard, which is fine by us and late for them.
Nothing changes in your stack.today: integrations mean migrations
A credential is a 220 KB file, not a dependency. No custody moves, no order flow touches us, no runtime call is required to display or check one. Verification runs offline, including inside your own systems.
How it plugs in.
Offline verifier
A single binary — or a self-contained HTML page — that re-derives every asserted property with no network. Ship it, embed it, or run it in CI: ./mizan-verifier bundle.bundle data.csv
The open standard
VTR-1 — 41 numbered requirements and nine known-answer conformance vectors, CC BY 4.0. You may implement it yourself, including against us. Read the standard →
Your data, or ours
Credentials bind to a canonical, provenance-pinned dataset. Your feed can become a canonical root so records mint against the data your users already trade.
The economics, stated plainly. Verification is free forever — running the verifier and checking a credential cost nothing, and charging for either would corrupt the statistics the standard exists to protect. Minting is the paid act, priced per credential, and free while the founding window is open. Where a platform brings volume, the commercial terms are a conversation, not a rate card.
What we will not do.
We do not take custody of anything, route orders, or hold client money — the referee never holds the money. We do not rate, rank or score your users against each other; we judge submitted computations against a fixed, public bar. We do not sign exclusivity: a standard that belongs to one platform is not a standard. And we do not publish anyone's failure without their consent — the refusals on our own wall are ours and public benchmarks, put there on purpose.
Bring one strategy and watch the gate work.
The fastest first step is not a meeting: run a credential end to end on your own data, verify it offline on your own machine, and decide afterwards whether the integration is interesting. If it is, we'll scope it in fifteen minutes.
TALK TO US →
Run one first →