Registry / Credentials / track-btc-trend-4h-link2

PROVEN

BTC-TREND-4H · LIVE TRACK · link 2 (+431 bars, chained)

BTC/USDT · 4h OHLC · 2017-08-17→2026-10-22 00:00 UTC (20,102 bars, +431 vs link 1)

A track record judged inside a zero-knowledge proof: returns after costs and every committed try recomputed in-circuit, the strategy never revealed. Don't trust this page: the proof re-runs offline on your own machine in about 81 ms.

Figures from the parent credential, the same committed strategy.

Download the proof ⤓Verify it yourself Embed the badge

MIZAN · VTR-1 credential#01c2fda4bc7839b8

Credential

BTC-TREND-4H · LIVE TRACK · link 2 (+431 bars, chained)

Verdict: Cleared
Class: Forward track
Engine: v11 · superseded
Anchor: Not anchored
Minted: 2026-10-22

Anchor fingerprint · SHA-25601c2fda4bc7839b8b1055054d2c6048febb9ee47673d4b9034e8583d53f1b007

Live status: PROVENfrom the public registryNot anchoredCheck it yourself ↗

What this proves

What the proof settles, and what it leaves open.

Forward extension: 432 bar(s) proven after a pre-registered, anchored commitment, so hindsight is impossible for those bars. Too short to be statistically meaningful on its own.

Proven

Returns after costs, recomputed inside a zero-knowledge proof on committed data.
The strategy stayed sealed. Nothing about how it works is disclosed by this credential.
Lookahead: impossible.

Not claimed

Hindsight: excluded for the bars after the Bitcoin-anchored commitment.
Not a forecast. It describes a record; it does not predict the next one.
Not advice or a rating of any person. A verdict on one record against one public bar.

Disclosed metrics

What the gate measured, after costs.

—No metrics disclosed

These figures are from the parent credential, the same committed strategy. This link re-proves it on the extended window (+431 bar) and discloses no separate metrics.

Cleared. The record passed the locked gate on committed data, after committed costs, out of sample. It proves the history was honest. It is a seal on a backtest, not a forecast.

The live track's second link: the same committed strategy re-proven over 20,102 bars, link 1's window a Merkle prefix of this one, link 1's digest bound in-proof. Every bar since 11 Aug 2026 post-dates the Bitcoin-anchored commitment. Verifier prints: 'track: parent 19671 bars -> this credential 20102 bars (+431)'.

The proof's journey

Five steps, each one checkable.

01 · CommittedData and spec

committed before the test

02 · ProvenEngine v11

220 KB proof · 2026-10-22

03 · TimestampedRFC-3161

—

04 · AnchoredNot anchored

01c2fda4bc7839b8b1055054…

05 · RegisteredLeaf #49

append-only, never removed

Chained:← parent · 19671 bars→ this credential · 20102 bars (+431)

Verify it yourself

Don't trust this page. Re-run the proof.

Download the proof bundle and the free, public verifier for your platform.
Turn the network off. The verifier needs no server, no trusted party, no MIZAN infrastructure.
Run the command. The verdict recomputes on your machine in about 81 ms and must match the one above.

The exact verify command

$ ./mizan-verifier-v11-macos-arm64 track_BTC_trend4h_link2_20261022.bundle btc_4h_full_ext3_20261022.csv --chain track_BTC_trend4h_link1_20260811.bundle --roots canonical_roots.txt --roots roots.txt

roots.txt: studio.mizan.market/api/catalog/roots.txt, the allowlist of canonical market data.

Chain record ↗Committed data ↗Roots ↗Verify page ↗The live wall ↗All credentials →

Carry it anywhere

One badge, checkable everywhere it appears.

The badge is live: it always shows this credential's current status, straight from the public registry. Free to display, at any volume.

For platforms →

Embed on a listing

<a href="https://mizan.market/credential/track-btc-trend-4h-link2/"><img src="https://studio.mizan.market/badge/track-btc-trend-4h-link2.svg" alt="MIZAN credential: BTC-TREND-4H · LIVE TRACK · link 2 (+431 bars, chained)" height="20"></a>

Or check it from code, or from an agent (MCP · A2A)

GET https://studio.mizan.market/api/agents/check?q=track-btc-trend-4h-link2
→ { "status": "PROVEN", "found": true, … }

The record

Every field, as committed.

Dataset: BTC/USDT · 4h OHLC · 2017-08-17→2026-10-22 00:00 UTC (20,102 bars, +431 vs link 1)
Minted (UTC): 2026-10-22T08:55:00Z
Verdict: PASS ✓ (extended window) — CHAINED: same committed spec · strict Merkle extension · parent digest bound
Kind: gate_pass_track
Engine era: v11 · both-schools validation-complete
Engine status: superseded
Credential hash: 01c2fda4bc7839b8
Anchor SHA-256: 01c2fda4bc7839b8b1055054d2c6048febb9ee47673d4b9034e8583d53f1b007
Bitcoin / OTS: pending (RFC-3161 landed 2026-10-22 08:55:53 UTC)
Registry leaf: 6efa7dde6ae8a5f007eadb9390001979a88647c9604883291e48defe2d04dd3e
Leaf index: 49
Registry root: 09607193c49aacf3b212f5e6da7d579b56f1b94db9bb553ebf97a6ab41b1c84a
Proof size: 220 KB

What a verdict means: what a PASS asserts · what we refuse to certify · reading a verdict · the VTR-1 standard.

Older credential →VERIFIABLE AI · MIZAN-NET-31 · OG (4-8-1 MLP, ReLU)

ENGINEv12 · 659bdb67… ● LIVE REGISTRY83 credentials · append-only VERIFY~81 ms · offline · trusting no one ANCHORBitcoin #962,013 SPECVTR-1 · frozen · CC BY ROOT09607193…b1c84a