Public integrity layer + private evidence + portable artifact + PQ verification.
H33's Avalanche story is not "we anchored 32 bytes." It is end-to-end provenance: a public chain commitment to a private off-chain bundle that anyone can verify independently, with no H33 contact required, using a downloadable Apache 2.0 verifier built from a reproducible recipe.
This proof reinforces the portable 74-byte post-quantum evidence primitive that H33-74 produces and anchors — it expresses that primitive against Avalanche; it does not redefine it. The off-chain bundle below verifies against the published binary today; the on-chain public-integrity layer is a validated fixture pending founder authorization (placeholder values shown below), not yet a live mainnet anchor.
The four layers
Layer 1 · Public Integrity
Single on-chain tx commits the SHA3-384 of the off-chain bundle. Anyone can fetch the tx from any Avalanche RPC and compare. Awaits four-field-paste founder authorization.
Layer 2 · Private Evidence
Self-contained JSON. Authority + policy + pipeline + model + corpus + evidence + citations + abstention bind into one signed artifact. Today: preview-grade signatures. Post-R1 ceremony: production PQ signatures from R1 root.
Layer 3 · Portable Artifact
Apache 2.0 verifier downloadable from h33.ai/verify/. Reproducible build (rust-toolchain.toml + Cargo.lock + SOURCE_DATE_EPOCH=0). Byte-identical across two independent runs.
Layer 4 · PQ Verification
ML-DSA + SLH-DSA signatures on the bundle (R1). PQ envelope on API delivery (R4 ceremony pending). Replay-detectable at envelope granularity; integrity-detectable at bundle granularity.
Mainnet anchor state
When founder authorization lands, the four placeholder values below are replaced with the real on-chain transaction details. The off-chain bundle's _preview_metadata.anchor_ref is updated; chain-aware verifiers add public-integrity verdict to their output.
- tx_hash:
- 0x0000000000000000000000000000000000000000000000000000000000000000 (pending)
- manifest_anchor_ref:
- 0x0000000000000000000000000000000000000000000000000000000000000000 (pending)
- customer_principal:
- PLACEHOLDER_PRINCIPAL (pending)
- anchored_at_ns:
- 0 (pending)
Founder four-field paste is held under terminal-directives lock 2026-06-06. When authorized, this section migrates to live values within minutes.
Try it now
The off-chain bundle verifies independently against the live published binary today. After mainnet anchor authorization, the same command output adds an on-chain match line.
curl -O https://h33.ai/bundles/avalanche-demo.json
curl -O https://h33.ai/bundles/avalanche-demo.sig.json # detached hash + ML-DSA-65 signature
curl -O https://h33.ai/verify/
chmod +x h33-verify-darwin-arm64
./h33-verify-darwin-arm64 avalanche-demo.json --mode summaryExpected: OVERALL: PASS WITH WARNINGS · exit 0 · H33 was not contacted during this verification.
Artifact status: the downloadable bundle is a validated fixture — a recorded, portable sample. The verifier binary and its verdict are LIVE (a real offline verification you run yourself). The on-chain match line is not present until mainnet anchor authorization lands. For independent verification, see Verification.
Why this matters
Anchoring 32 bytes on a public chain is not a moat — every chain offers it. What is differentiated is the COMPOSITION: a publicly-anchored commitment to a privately-signed off-chain bundle, where the bundle is portable across systems, verifiable without contacting the issuer, and PQ-future-proofed for the lifetime of the underlying asset. That composition is what makes H33 evidence acceptable to issuers, custodians, regulators, and auditors simultaneously.
Bundle + Anchor + Verifier all agree. No H33 contact required.
Related proofs of the same H33-74 primitive: Bitcoin Mainnet Attestation · Biometric Auth · Encrypted Biometric Verification.