A trader's rank, a PM candidate's history, a strategy's tearsheet — your users read all of it as something you stand behind, because you are the one displaying it. So the risk of every unverifiable record on your platform sits with your brand, and the only tools available for managing it are your own attestations. You vouch, therefore you carry it.
MIZAN removes that position. Records become portable, cryptographically verifiable credentials checked against an open standard — not against your servers, and not against ours. Your users verify them offline, trusting neither of us. When a listing disappoints, the standard answered, not your brand.
A marketplace will never adopt a standard owned by a competing marketplace. That is why every attempt to make verification a feature has stayed inside one company's walls and stayed worthless outside them.
MIZAN can never take your customers. We do not list strategies, do not allocate, do not custody, do not execute, and never rate people. The specification is CC BY — you may implement it without asking us, including if you compete with us. The reference verifier is source-available. The registry API is public and free. Neutrality here is not a moral position; it is the reason adopting us is safe.
If you have already assembled a community of quants or allocators, you have the hard half of a marketplace. What you lack is the layer that makes listings believable to someone who does not know you. You can launch a verified venue of your own on this standard: credential issuance, the gate, the chain, and verified listings — while you own the community, the relationship and the business.
Open a full book-level credential → — what a listing on your venue would carry.
Economics are aligned to outcomes rather than to listings: a share of the performance fee earned on capital routed against a credential, above a high-water mark, only when the credential delivered the result. We never hold the money and never pick the manager.
The marketplace capability is a contemplated feature and may require licensing in relevant jurisdictions; it will not be offered until authorised. Money always moves through the operator's own licensed rails, never through ours.
| Step | What it is | Effort |
|---|---|---|
| Display | Show a "VTR-1 verified" state on listings that carry a credential; users click through to a public credential page. | Hours |
| Verify | Re-check credentials client-side or against the free public registry API — trusting neither us nor your own backend. | A weekend |
| Bridge | Export your users' strategies to the submission spec, or emit committed position streams for the sealed path where the model never leaves its author's machine. | Weeks |
| Require | Make a credential a condition of listing. This is where the flywheel starts: every member mints, the wall grows, and your listings become the checkable ones in your category. | A decision, not a build |
Engineering documentation, conformance vectors, the reference verifier and the registry API are public and need no conversation with us: build on the standard → · conformance detail → · reproduce a credential in ~200 lines →
Not a partnership, not a term sheet — one listing, one credential, one measurable difference in how your users treat it. We will run the first credential for you and help wire the display. If your users do not behave differently, you have lost an afternoon and we have learned something worth more than a logo on a slide.
MIZAN is a verification and technology provider. It does not custody, execute, allocate, or advise on capital, and issues no investment recommendation. Credentials attest to the honesty of a computation on committed data — not to future performance. Compliance, licensing and suitability obligations on your platform remain yours. · for quants → · for allocators → · the frozen spec →