VTR-1 is open by design: the spec is CC BY, the reference verifier is source-available, the conformance vectors are public, and the registry API is free. Verification is free for everyone, forever — offline, in-browser, in your product. What follows are the five doors in, from a weekend verifier port to extending the standard itself. GIPS didn't win because its authors built everything; it won because everyone else built on it until "are you compliant?" became automatic. That is the finish line here.
Write an independent VTR-1 verifier in any language. The spec's 41 numbered requirements (R-01 … R-41) plus the 9 public conformance vectors mean your implementation is checkable against a public test set rather than against our word. Every independent implementation makes the standard more real and every credential more portable — a second implementation is the single most valuable thing an outside engineer can contribute.
Your product's problem is trust in performance numbers that are self-reported today. Embed a "VTR-1 verified" check: listings carry credentials, your users re-verify them client-side or against the public registry API — trusting neither you nor us. Displaying and checking credentials is free at any scale. When your quants issue credentials at volume, issuance is licensed — that conversation lives on the partners page.
Any strategy language or backtesting framework can grow a "mint a credential" export: compile your format to the MIZAN submission spec (open rules DSL), or — for logic the DSL can't express — emit the committed position stream for the sealed path, where the strategy never leaves its author's machine. The first external bridge (an open-source trading language) is in flight now; yours can be second.
Wire minting into your research pipeline: every promoted strategy version automatically commits, proves against the locked gate, and chains its existing track forward as data accrues — the credential stops being a ceremony and becomes a routine build artifact your allocators can re-verify. Our own registry runs this way: the live track's chain extension fires automatically when its bar closes. Hosted minting via the app; fully-local minting via the offline engine for teams whose strategies never touch anyone's servers.
VTR-1 is versioned and its evolution is public: propose a gate class for a new mandate (market-neutral shipped as the second class; yours could be third), a new statistical arm, or a v1.x extension. Frozen text changes only by erratum or new version — the era registry is append-only, so nothing you build on today's standard can be revoked out from under you. Replication studies and teaching material (a course capstone that mints a real credential) are extensions too, and the most welcome kind.
Verifying — offline, in-browser, in your product, at any scale. The spec (CC BY). The conformance vectors. The registry API.
Issuing credentials through our prover — per credential, at platform volume.
The spec permits independent issuers — a standard nobody else may implement is just a proprietary format; a rival implementation is checkable against the public vectors rather than its own marketing.
The neutrality — one locked gate identical for everyone, refusals published, an append-only era registry. Anyone who profits from the strategies being judged is structurally conflicted out of judging them.
The referee never plays. That is why every player can build here.
Building something on VTR-1 — or stuck on the spec? Write: [email protected]. Founding-window quants: the 25 named founding seats are the last free ones.