"Twelve engine eras" appears across this estate (it read "eleven" until 14 October 2026, when the twelfth was stamped live). This page is what the phrase points at. The count is the verifier series: eleven numbered releases of the proving engine between 2 July and 25 July 2026, each with an archived binary, and a twelfth, frozen 13 October and stamped live 14 October 2026. Seven were promoted to canonical guest eras in the append-only era registry that every verifier carries inside it. Five of those seven have a guest image id recomputed from the archived ELF; one (v5) carries the id embedded in its archived verifier, stated as such; one (era_a) has none, and this page says so rather than guessing. The rest were format or interim builds. Nothing here asks to be believed; download a binary and hash it.
A credential commits the image id of the guest that judged it. The verifier resolves that id against this registry and prints the era. An unrecognised id prints a warning; a cloned guest cannot pass as a MIZAN era. Superseded eras stay verifiable forever against their own archived verifier.
genesis flagship
Genesis flagship — first real-STARK MIZAN credential: in-circuit RiskGate attestation (PASS/FAIL + data root + strategy commitment, strategy never revealed). Bitcoin (OpenTimestamps) + RFC-3161 anchoring arrived with the v5-era re-mint of the same flagship on 18 July (see v5).
null · no canonical ELF archived for this era; the id was not re-derived and is not guessednullb49ac4a9d2448088296b2e64abe1c64b2298282b2603ef2d59e90a1bd4a926bbbin_era_archive/verifier-era-a-20260711 · recomputed now: matchesmizan-verifier-macos-arm64 · same hashbin_era_archive/era_a_flagship/credential_REAL.bundle · sha256 d6bed70cfc3f97bcce4f80aa9646296f184dc9ebdf9063af7ed085abc8def681 · minted archived 2026-07-12 (repair of the 07-08 overwrite, git 3fef3f5) · PASS · re-verified 2026-10-13 with verifier-era-a-20260711 against data/btc_4h.csv, exit 0 · no anchor file exists for this bundlearchived flagship credential + verifier binary; no canonical ELF archived, so the image id was not re-derived. 2026-10-13 reconciliation: the .ots/.tsr/anchor.json formerly in this folder record sha d9b01ce4… and belong to the v5-era re-mint (moved to era_a_flagship/v5_remint_anchor/, README there). Registry metadata corrected; no hash or era label altered.black-box + zkml, one-guest mode envelope
In-circuit black-box gate (gate computed over a pre-committed forward position stream; model opaque) + zkml proven inference (committed compact model's own decisions through the gate). ProverSpec mode envelope: one guest, one image id, three families.
dc3ee0310eee4a2487583238945694b62cccc01be941ac9a016f329349f0a254verifier-embedded · read from the allowlist embedded in the archived verifier, which accepts the reference credential; NOT recomputed from an ELFbea2090a9d87b609d508bc24142e44e6dcb8d8be607dacd5d064d105cc68a20bbin_era_archive/verifier-era-v5-20260718 · recomputed now: matchesmizan-verifier-v3-macos-arm64 · same hashbin_era_archive/era_a_flagship/v5_remint_anchor/credential_REAL.bundle · sha256 d9b01ce4e63124d9ff45b1a36d64aba84094a42f92d9b036ce016942eb12f540 · minted 2026-07-18 (flagship re-mint on guest v5) · PASS · re-verified 2026-10-13 with verifier-era-v5-20260718 against data/btc_4h.csv, exit 0, image id ✓ · RFC-3161 TSA freetsa.org 2026-07-18 08:52:19 UTC · OpenTimestamps state pendingarchived host + verifier binaries only; no canonical ELF archived, so the id was NOT recomputed. Image id recorded 2026-10-13 from the allowlist embedded in the archived v5 verifier, which accepts the reference credential carrying it ([✓]); the same id is in docs/GUEST_V5_FULL_BLACKBOX_ZKML.md and data/engine_ids.json. The earlier partial 'd0f331e1…' in the GPU runbook does not match and was never recorded.+ DSR class (deflated Sharpe)
v5 + DSR class: deflated Sharpe ratio with N committed and every trial's Sharpe re-derived and bound in-circuit over one committed trial ledger (Bailey-Lopez de Prado).
12b2f0429fdec5ae4dd40c6284a05b60f00320a784364c0b1fff526f5bd9f481computed · recomputed with risc0 compute_image_id from the archived ELF179bed22c78c025ab7e13219e95bd8e2cd53eab52986c15bedca541b2d8a5c04bin_era_archive/verifier-era-v6-20260720 · recomputed now: matchesmizan-verifier-v4-macos-arm64 · same hash+ audit-hardened PBO + CPCV
v6 + audit-hardened PBO (probability of backtest overfitting, CSCV) and CPCV (purged + embargoed combinatorial cross-validation, leak-free), minted on H100, verified, anchored, public.
b9dc68467927d2cdda424b4747ddc3b8c3c4255a9150b889e027caf276a30d86computed · recomputed with risc0 compute_image_id from the archived ELF85d453b48acaf7cce93878ca80160cf147b870aecb23eabb4f886f76bfb346e6bin_era_archive/era_v9/verifier-v9-20260722 · recomputed now: matchesmizan-verifier-v9-macos-arm64 · same hashcomposed PBO S=16, n_eff DSR, fractional sizing
Composed PBO at S=16 (all 12,870 balanced partitions, per-trial proofs verified in-circuit), n_eff DSR, fractional sealed-model sizing. Minted, verified, red-teamed, anchored, public. Was the live public era 2026-07-22 → 2026-07-25; superseded by v11.
dafad185fe3e00797e4033b5e93171748d7937c33ecf9e452fb73702448aaed7computed · recomputed with risc0 compute_image_id from the archived ELF8d0962f2dbb93adb9f805e07841aade539c23b31e7797ff7edfd50f6d8a4030fbin_era_archive/era_v10/verifier-v10-20260722 · recomputed now: matchesmizan-verifier-v10-macos-arm64 · same hashSuperseded by v11 on 2026-07-25 but STAYS VERIFIABLE FOREVER (append-only): every v10 credential (e.g. data/credential.bundle) verifies against this era's archived verifier for all time. canonical_method_v10.bin and this verifier binary are never altered. Image id was also confirmed on the running prover /health and matched the public verifier download while v10 was live.both-schools validation-complete
LdP-complete + Harvey-Liu/Hansen SPA (both-schools validation-complete): ValidationExt (PSR + MinBTL + Harvey-Liu + SPA over one committed ledger, salt-grind-proof SPA seed v2) + LabelSchema / Structural / HRP attestations (AttestCredential v3, MZATTB1 magic) + full verifier re-derivation of every committed statistic. THE CURRENT LIVE PUBLIC ERA (stamped 2026-07-25).
3ac3b10b7930324d58948020c827bb2447bdb3d8eff85eb6a2fd10fb5214237bcomputed · recomputed with risc0 compute_image_id from the archived ELFd154099d0fb2390c243822b49fc1e0a028ae244a0fe32c2f1293aff08cf15256bin_era_archive/era_v11/verifier-v11-20260725 · recomputed now: matchesmizan-verifier-v11-macos-arm64 · sha256 c623e574977120790421c9af56349485f2d555676eca8d2bba15c4d93844f6a3 · same guest image id, rebuilt 2026-08-12mizan-verifier-v11-linux-x86_64 · sha256 453243b4849cb2d1dfbb7198ec9151ef2ae1cbf900a055ace7165c443398565c · same guest image id, rebuilt 2026-10-13 (static musl, verified on Linux against v11 credentials)mizan-verifier-v11-windows-x86_64.exe · sha256 e8d9fc183765accdf2969c8ae1646db1de151f4ffb440a53e218559daac2fa0a · same guest image id, rebuilt 2026-10-13 (verified on Windows Server 2025 against v11 credentials, tamper detected)data/credential_vext_gpu.bundle · sha256 6cebaa914f95f69a4995a9afdd4e5e46ce8ea2c16c729afda35696df9fa63c98 · minted 2026-07-25 · NOT SIGNIFICANT — PSR 0.7226 < 0.95 (printed, never hidden); MinBTL / Harvey-Liu (BHY p 0.0118) / SPA (p 0.0050) all PASS. Independently re-verified with the candidate verifier at exit 0.Stamped live 2026-07-25 (era_v11_CANDIDATE frozen to era_v11). Verifier rebuilt from the registry-carrying source with statuses at stamp (v11 live, v10 superseded); mizan-core untouched so image id stays 3ac3b10b…. Re-verifies data/credential_vext_gpu.bundle at exit 0 with the era line. The verifier embeds this registry via include_str!, so verifier_sha256 states the archived binary's own file hash (external download-integrity reference; verification logic never reads this field). Superseded by v12 on 2026-10-13 but STAYS VERIFIABLE FOREVER (append-only): every v11 credential verifies against this era's archived verifier for all time.any-agent books · completion statistics · cost floor in-circuit · bracket exits
v12 — (1) ValidationExt2 stamped: MinTRL, robust-Sharpe block bootstrap, Model Confidence Set, trial-correlation (ρ̄ + Kish N_eff) disclosure, every number re-derived by the verifier; (2) protocol cost floor enforced INSIDE the circuit (gate min_cost_bps clamped to 10 bps before evaluation; sub-floor declared costs fail CostTooLow in-proof); (3) BlackBoxBook: multi-asset forward-committed per-asset position streams (any agent whose decisions are a position vector per bar), gross cap enforced in-circuit, turnover charged on every size change, track head re-derived and sealed; (4) rules-DSL bracket exits (profit-take / stop / time), CLOSE-evaluated, never an intrabar fill, inside the salted strategy commitment.
659bdb678a3d7a2695017b216417ac32eb11fee28a2ea649317d83ef74830d51computed · recomputed with risc0 compute_image_id from the archived ELFfaf4c58f15fcb6f62e7c37bd2e4777dba36991e9f7db13d94884fbfd7b4d16babin_era_archive/era_v12/verifier-v12-macos-arm64-20261014 · recomputed now: matchesmizan-verifier-v12-macos-arm64 · same hashStamped live 2026-10-14 IST (candidate frozen 2026-10-13) (era_v12_CANDIDATE frozen to era_v12). Image id recomputed from three byte-identical builds; real H100 mints (agent book, flagship track, legend refusal, ValidationExt2) verified at exit 0 with this verifier on macOS, and with the Linux and Windows builds. Spec: docs/ERA_V12_SPEC.md. The verifier embeds this registry via include_str!, so verifier_sha256 states the archived binary's own file hash (download-integrity reference; verification logic never reads this field).Numbered as the verifier binaries were published on the verify page. The site's numbering is the release order, not the guest era name: release 3 is guest era v5, release 4 is guest era v6. Hashes are of the files served today. Where no binary was published, the row says so.
b49ac4a9d2448088…d137676832cc2fd1…bea2090a9d87b609…179bed22c78c025a…no public binaryno public binary75d01154b9cd91eb…ee4e831f517efebb…85d453b48acaf7cc…8d0962f2dbb93adb…c623e57497712079…faf4c58f15fcb6f6…Dates for releases 7 and 8 are the commit dates of the DSR hardening and audit-closure work they shipped; their canonical ELFs were not archived, so they carry no image id. Release 1 is served as the unversioned original binary. Release 11 served today is the 12 August rebuild of the v11 verifier with the same guest image id and updated era statuses; the stamp-day binary hash is in § 01.
The prover source is private by design: free to verify, paid to mint. What can be measured about it without reading it:
The line count is a claim you cannot check, and it stays labelled as one. The verifier binaries are not: hash any of them against this page. The guest image ids are not: recompute them from an archived ELF on request. The registry is not: every credential on the wall commits one of these ids.
8d0962f2dbb93adb9f805e07841aade539c23b31e7797ff7edfd50f6d8a4030f · published as mizan-verifier-v10-macos-arm64d154099d0fb2390c243822b49fc1e0a028ae244a0fe32c2f1293aff08cf1525638109a412577c00734c3ac9c9a8ab2b8aaa37ff94c738c1ac347d4620cd5fab02796c9c935e56aa6726ab7a1b9f5eaf60e297563dc4d2672a72e398e5947aa53c623e574977120790421c9af56349485f2d555676eca8d2bba15c4d93844f6a3 · published as mizan-verifier-v11-macos-arm64453243b4849cb2d1dfbb7198ec9151ef2ae1cbf900a055ace7165c443398565c · published as mizan-verifier-v11-linux-x86_64e8d9fc183765accdf2969c8ae1646db1de151f4ffb440a53e218559daac2fa0a · published as mizan-verifier-v11-windows-x86_64.exe117202e91f8868733e9cfb54068338c10a91dd7293e29ebaae0a975f2e1afa97 · published as mizan-verifier-v12-linux-x86_64faf4c58f15fcb6f62e7c37bd2e4777dba36991e9f7db13d94884fbfd7b4d16ba · published as mizan-verifier-v12-macos-arm64a1585dcbf50ac2f417acc20048747fb262ff8acfce612737e5f892e73acc6773 · published as mizan-verifier-v12-windows-x86_64.exe85d453b48acaf7cce93878ca80160cf147b870aecb23eabb4f886f76bfb346e6 · published as mizan-verifier-v9-macos-arm64b49ac4a9d2448088296b2e64abe1c64b2298282b2603ef2d59e90a1bd4a926bb · published as mizan-verifier-macos-arm64bea2090a9d87b609d508bc24142e44e6dcb8d8be607dacd5d064d105cc68a20b · published as mizan-verifier-v3-macos-arm64179bed22c78c025ab7e13219e95bd8e2cd53eab52986c15bedca541b2d8a5c04 · published as mizan-verifier-v4-macos-arm64d137676832cc2fd1075dda314126f938a75db68416ad96f73c04ffd2ee096be1 · published as mizan-verifier-v2-macos-arm64c8dffa3d1410e1e54c1b8ae5ebc34a0789f25f344ef461f5c2a1f1d2830fa0bc87d0e1b020528610df25de3e55230c4b5ee80f4639068c1b6432160084fa8114Read with: errata · the security review · the retraction ledger · what is new here, and what is not.