Post-Quantum Primitive · Architecture layer: ROOT

H33-74

Name: H33 Substrate
Author: H33

The 74-byte post-quantum attestation substrate that makes operational evidence portable across blockchains, verifiable independently of the operator, and durable through the quantum transition.

Definition. H33-74 is a 74-byte post-quantum attestation: a 32-byte SHA3-256 commitment anchored on-chain plus a 42-byte compact receipt kept off-chain, together signed under three independent NIST post-quantum signature families (ML-DSA, FALCON, SLH-DSA). It is a primitive — a small, fixed-size object other systems build on — not a product or a service.

How it works

from graph: concept:H33_74 · USES ML_DSA + FALCON + SLH_DSA · whitepaper §byte-structure

Any operational event — a decision, a computation result, a state change — is committed to a fixed 74-byte footprint that never grows, no matter how large the evidence behind it. The footprint splits cleanly into two halves:

Component	Size	Where it lives	What it is
On-chain commitment	32 bytes	anchored on any chain	SHA3-256 digest of the full attestation receipt
Compact receipt	42 bytes	off-chain, portable	version + domain separator + signature flags + locator
Persistent footprint	74 bytes	total	the H33-74 attestation

The receipt is signed under three independent NIST families at once — ML-DSA (lattice, FIPS 204), FALCON (NTRU-lattice), and SLH-DSA (hash-based, FIPS 205). Three families on different hardness assumptions means an attestation stays unforgeable even if one family is later broken.

Why 74 bytes matters

from graph: H33_74 ANCHORS_TO {chains} · on-chain footprint vs raw PQ signatures

Anchoring the raw post-quantum signatures on-chain is impractical. H33-74 anchors a single 32-byte commitment instead — smaller than the 64-byte Schnorr signatures Bitcoin already carries. Anchoring adds no cost; it subtracts it.

On-chain footprint	Per attestation	1B attestations	Families covered
H33-74 (on-chain commitment)	32 bytes	32 GB	3
ML-DSA signature on-chain	3,309 bytes	3.3 TB	1
All three families on-chain	21,054 bytes	21 TB	3

What proves it

from graph: H33_74 DOCUMENTED_BY /benchmarks/ + /schemas/ · PROOF_PAGE_IS_NOT_PROOF_ARTIFACT

Every claim resolves to a reproducible artifact, never to marketing copy. Performance and wire-format evidence live in dedicated, independently-reproducible surfaces:

Benchmarks

Signing and verification timings under the fixed footprint, with per-result cost decaying O(1/N) under batched Merkle aggregation — /benchmarks/.

Receipt schema

The byte-exact wire format (commitment at bytes 0–31, signature flags) — /schemas/h33-74/ and the receipt spec.

How anyone verifies it — with H33 not in the loop

from graph: H33_74 VERIFIED_BY VERIFIER · VERIFICATION USES H33_74 as artifact substrate

An attestation is checked by an independent, open verifier you download and run offline. It recomputes the 32-byte commitment from the receipt, checks all three post-quantum signatures, and confirms the on-chain anchor — with no contact to H33. Certainty rests in the bytes and a conformance-attested verifier, never an H33 service. The direction is acyclic: verifier → verifies → attestation → proves → claim.

How verification works → · The independent verifier →

What builds on it

from graph: inbound USES / BUILT_ON H33_74

H33-74 is the ROOT substrate — the one primitive nearly everything above it consumes:

Agent-008	emits a Provable Authority Package on the H33-74 substrate
HATS	continuous attestation records built on H33-74
APQC	every migration phase produces H33-74-signed evidence
Authority Center	authority state preserved as replayable H33-74 evidence
PQ-Verified	its artifact is built on the H33-74 footprint

What it produces

from graph: H33_74 PRODUCES attestation-receipt (issuer tooling)

H33-74 issues one thing: the 74-byte attestation. The issuer takes any evidence bundle, distills it to the fixed footprint, signs it under the three families, and returns a portable receipt plus its 32-byte anchor — the same object regardless of who produced it or which chain it anchors to. Download the issuer + verifier →

Where it anchors — portability, not migration

from graph: H33_74 ANCHORS_TO {Bitcoin, Ethereum, Solana, Zcash, Avalanche, …}

One receipt anchors to many chains without being rewritten. The evidence is never bound to any chain — the chain is an interchangeable notarization anchor, so the evidence survives chain migration, deprecation, or a chain disappearing entirely.

Chain	Anchor method	On-chain	Consensus change
Bitcoin	Taproot (P2TR) / OP_RETURN	32 bytes	None
Solana	PDA	32 bytes	None
Ethereum / L2s	calldata / log	32 bytes	None
Zcash, Avalanche, Polygon …	native anchor	32 bytes	None

One receipt, three chains, zero migration →

Next step

from graph: H33_74 CONVERTS_TO (via products) EVALUATION_PATH

H33-74 is a primitive — you adopt it through the products built on it, or evaluate it directly.

See H33-74 prove your evidence

Deep reference

from graph: H33_74 DOCUMENTED_BY whitepaper + schema + spec

Technical whitepaper (formal specification) · Receipt schema v1.0 · Attestation receipt spec · Benchmarks

Related architecture, comparisons & applications

Architecture: Portable artifact architecture · Evidence bundles (downloads)

Comparisons: H33 vs blockchain audit-trail tools

Applications & proofs: H33 self-attestation · The end of the blockchain era (Proof Lab)