VTR-1 v1.0 — FINAL (frozen 1 Aug 2026) · The Verifiable Track Record Standard

VTR-1, Version 1.0 — FINAL. Frozen 1 August 2026.

An open specification for verifiable track records: a trading performance claim proven honest by cryptographic proof rather than asserted by its author. CC BY 4.0 — anyone may implement, cite, or extend it with attribution, including parties who compete with its steward.

Frozen artifact digest

SHA-256  29b43d426bfc315fd3c1e366ef585fca6e17610bd46c33a79b217890a8bd58e9  VTR-1_Standard_v1.0.pdf
SHA-256  851f33379ec9ed9b70a1096d30a31391e45ec1cd245132f44683de434194afb7  VTR-1_Conformance_Vectors_v1.0.tar.gz

A copy that hashes differently is not this version. Both artifacts are timestamped on Bitcoin (OpenTimestamps); .ots proofs are attached.

Contents — 22 pages. Three conformance Levels, the verification procedure, the boundaries the standard refuses to certify, governance under era law, an adversary model with seven named attack classes, strategy representation, and normative appendices pinning the estimators, the fixed-point arithmetic and the commitment constructions. 41 numbered requirements (R-01 to R-41), so a conformance claim can be contradicted.

Conformance vectors — nine known-answer tests with normative exit codes: five that MUST verify, three that MUST NOT, and one published honest failure. They exist to make an independent second implementation cheaper to build.

Frozen — the normative text will not change. Findings are published as errata with attribution; a finding that alters a requirement produces a numbered successor version which supersedes but never invalidates credentials issued under this one. Requirement identifiers are permanent.

Canonical text: https://mizan.market/standard-spec
Errata and soundness reports: muavia@mizan.market

Estate Mirror 2026-07-31 — credentials outlive the issuer

MIZAN Estate Mirror — 2026-07-31

Purpose: issuer-irrelevance, made true. A MIZAN credential names its judging engine era and verifies against it forever. This release mirrors the complete verification estate off-domain so that every existing credential remains verifiable even if mizan.market ceases to exist. Verification requires no MIZAN server, no MIZAN goodwill, and no MIZAN survival.

Contents

• era-archive.tar.gz — every archived engine era: verifier + host binaries (v10 dafad185…, v11 3ac3b10b… incl. the 20260729 own-data-tier build) and era-pinned canonical methods. Old eras are superseded, never revoked.
• credential-bundles.tar.gz — the public credential bundles with their OpenTimestamps (.ots), RFC-3161 (.tsr), and anchor sidecars. The .ots files carry embedded Bitcoin block-header attestations.
• exhibits.tar.gz — the pass/honest-FAIL exhibits (BTC-TREND-4H PASS; the founder's own SPY strategy, refused).
• canonical_method_v{9,10,11}.bin — era-pinned method commitments.
• btc_daily_canonical.csv, btc_daily.csv, btc_4h.csv, btc_4h_full.csv — canonical crypto datasets (Binance-derived public market data). Re-derive the Merkle root from these and it must match the root inside the proof.
• MANIFEST.sha256 — sha256 of every asset in this release.

Deliberately excluded

US equity datasets (Sharadar-derived): redistribution terms not yet confirmed in writing — excluded until they are. Verifiers holding a licensed copy can verify those credentials against their own data via the own-data tier (--any-data); matching roots prove the data identical. Withdrawn datasets (NIFTY, GOLDBEES) are excluded because MIZAN no longer vouches for their source; their existing credentials verify forever under era law.

Verify a credential offline

1. Extract the era the credential names. 2. Run that era's verifier against the bundle. 3. Re-derive the data root from your own copy of the dataset. 4. Check the .ots against the Bitcoin blockchain. No step involves mizan.market.

License: binaries and bundles are provided for verification. Market data is exchange-originated public data.