ميزانMIZAN ← RegistryGet in touch
Verified credential · public record

BTC-TREND CPCV · purged+embargoed (leak-free)

P05 PATH SHARPE +0.003 · POSITIVE CPCV validation arm (purged + embargoed) engine era · v11 · both-schools validation-complete

A cryptographic credential on the MIZAN registry — every number below is committed inside a zero-knowledge proof and re-derived by an independent verifier. The strategy itself is never revealed.

https://studio.mizan.market/credential/cpcv11-flagship
Attested by proof#cpcv11-flagshi
STARK sealverified — no trusted setup, re-checkable by anyone
Committed journalbound to this credential — one changed byte and every verifier rejects it
Engine erarecognized — v11 · image 3ac3b10b7930 (append-only era registry)
Committed inputstrial matrix Merkle-committed — verdict recomputed in-circuit
Independent re-verificationpassed on the standalone era verifier
The strategy itselfnever revealed — sealed by construction
Committed metrics · re-derived by the verifier
P05 path Sharpe0.003
Paths15
Bars purged160
What this proves · what it does not
Provesthe committed computation ran on the pinned data under the locked gate — net of the committed, disclosed costs
Does not provefuture returns · deployable capacity · real-world fills beyond the committed cost model · transfer to other assets or windows · robustness to search multiplicity — a separate credential class, and one our own flagship fails
Trial count Nnot bound on this credential — the ledger binding is carried by deflated-Sharpe and validation credentials
Holder recordnot opted in — this holder has not elected to publish their complete record
Credential record
Credential idcpcv11-flagship
KindCPCV credential
IssuerMIZAN
DatasetBTC · 4h OHLC · 2020–26 (12,917 bars)
Minted (UTC)2026-07-25T16:20:00Z
Proof size220 KB · STARK
Credential digeste8bc315a5566676a…
Committed engine image3ac3b10b7930…
Anchored in time
RFC-3161 timestamp (TSA)Jul 25 22:22:03 2026 GMT
Bitcoin anchor (OpenTimestamps)confirmed · Bitcoin block 959613
Anchored SHA-256e8bc315a5566676a12e28eac1ca79cb4…
Re-verified from the bundle · curated registry entry
Verifier runmizan-verifier-v11-macos-arm64 · exit 0 · 11 checks · 2026-10-29T13:57:03Z
Verifier binary sha256c623e574977120790421c9af56349485…
Bundle sha256 · sizee8bc315a5566676a12e28eac1ca79cb4… · 225,341 bytes
Series · btc_4hsha256 0db9a1f4bf55029c… · root 67d217b385d55d61…
Anchors on diskRFC-3161 .tsr ✓ · OpenTimestamps .ots ✓ (Bitcoin attestation upgrades automatically)

This block is produced by running the published era verifier on the stored bundle and the catalogue series each time the cache expires — the page is rendered from the proof, not from a template.

Re-verify it yourself — zero trust in us

The verdict on this page is not an assertion by MIZAN — it is recomputed on your machine from the proof bundle. Download the bundle, grab the pinned era verifier and the canonical dataset from the Verify page, and run:

macOS (Apple silicon)
./mizan-verifier-v11-macos-arm64 mizan_cpcv_v11.bundle btc_4h.csv --cpcvcopy
Linux x86-64
./mizan-verifier-v11-linux-x86_64 mizan_cpcv_v11.bundle btc_4h.csv --cpcvcopy
Windows x86-64
.\mizan-verifier-v11-windows-x86_64.exe mizan_cpcv_v11.bundle btc_4h.csv --cpcvcopy

Minted after your verifier was published? Pass --roots canonical_roots.txt (from the catalogue) so a newer market or book root pins too.

Carry it
Status todayGOOD
Transparency logleaf · proof at /api/log/proof-for/cpcv11-flagship
Signed receiptLog proofStatus

The receipt is an EdDSA token for your agent card or ERC-8004 record, verified offline with the published key. A venue can require it in twenty lines (mizan.market/skill/REQUIRE.md).

Show this credential
MIZAN credential badge
Embed options
The badge reads the live registry and always shows the verdict as issued, including a refusal.
Prove yours
Send positions only. Your model never leaves your machine. The first preview is free and private.
Agents: MCP https://studio.mizan.market/mcp · tool preview_credential · onboarding /api/agents/start
Prove a track record
Minted by engine era v11 — append-only era registry: a credential verifies against its own era's engine id forever; superseded ≠ revoked. How the Standard works →

ميزان  MIZAN · Proof of performance for every agent that claims results · Mizan Verification, Inc.
Every claim on this page is re-derivable from the proof bundle by anyone, trusting no one — including us.
Prove the edge. Never reveal the strategy.