Agent-008 — Agent GovernanceHATS — Cyber InsuranceH33-74 — Portable ProofPQ Verified — PQ ValidationCryptographic APIs
AIR
The Cryptographic Lifecycle
How It WorksWatch DemoThe MapPatent Portfolio
Architecture
H33-RootAgent-ZeroQ-SignReplayTruth
Cryptographic Services
UpstreamFHE-IQBFVCKKSTFHE
Open Standards
HATSHICSPQ-Verified (New)CRVOISQ-Key
Verification
Conformance SuiteVerification GuaranteesHATS SpecificationArchitectureProtocol Stability
Proof Lab
Cyber Insurance (HATS)BankingGovernmentHealthcareLaw FirmsPayments (WireProof)AI Companies
SDKs & Tools
SDKs HubTypeScript SDKMCP SDKVerifier CLIGitHub
References
DocumentationAPI ReferenceConformance VectorsSchemasBenchmarks
AboutPressPartnersPricingContactLegal
StartEcosystem
White PapersBenchmarksProofsResearch Overview
Explore (579)Live Systems (52)Pricing
Log InGet API Key✓ Verify It Yourself
H33 H33-74 ← All one-pagers Screen-shot the card · Cmd+Shift+4 · paste to LinkedIn
H33
H33-74Chain-Portable Evidence
For CIOs & CTOs

"Vendor and chain decisions become architectural commitments we can't reverse."

Infrastructure becomes replaceable below the evidence layer.

Related · tier-1 reading. For what a portable artifact actually is, see Portable Artifact.

01

Chain portability by construction

Receipts are valid without any chain anchor. Anchor on one chain, many chains, or no chain. Migration is no longer a category of work.

02

Start without a chain

Produce verifiable receipts before chain selection. Select the chain when business and regulatory considerations align, not as a foundational decision.

03

Three integration patterns

Policy engine, system-of-record wrap, integration bus. Pick the level of invasiveness that fits the existing architecture.

04

Open-source verifier

No operator-infrastructure dependency for audit. The H33 verifier runs without H33 being a going concern.

The asset may move.
The evidence remains.
h33.ai/h33-74
H33-74 · Post-Quantum Evidence

H33-74 in brief — for the CIO / CTO

H33-74 is the portable 74-byte post-quantum evidence primitive — a 32-byte on-chain commitment plus a 42-byte off-chain receipt, signed under three independent NIST post-quantum signature families (ML-DSA, FALCON, SLH-DSA) — that produces and anchors a self-contained proof. It is a fixed-size object your systems build on. For a CIO/CTO it puts the evidence layer above the infrastructure, so chain and vendor choices become reversible deployment decisions instead of one-way architectural commitments.

What it is not. H33-74 is a primitive, not a service. It is not continuous monitoring (that is HATS), not the verification verdict (that is Verification), and not agent governance (that is Agent-008). The blockchain is only an interchangeable anchor — the evidence is never bound to it.

Why does a CIO/CTO care?

Receipts are valid with no chain anchor, so you can start before selecting a chain and migrate later with no rework. Migration stops being a category of work.

How does it integrate?

Three patterns — policy engine, system-of-record wrap, or integration bus — let you pick the level of invasiveness that fits the existing architecture.

What proves it?

Byte-exact wire format at /schemas/h33-74/ and reproducible timings at /benchmarks/. Verification is an open verifier you download and run offline.

Is audit dependent on H33?

No. The verifier is open-source and runs without H33 being a going concern, so evidence has no operator-infrastructure dependency.

Go deeper: What H33-74 is & how it works · How verification works · For the CISO · For the CFO