H33-74

An introduction to H33-74.

Watch: H33-74 — Universal Post-Quantum Verification Substrate →

How it works

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:

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

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.

How H33 makes post-quantum scale — the measured byte collapse →

Artifact size: how 74 bytes compares with an ordinary log record

A frequent question is how the attestation compares with the log line a system would otherwise write. Conventional structured log records commonly run on the order of 100–300 bytes. Against that range, a 74-byte attestation is roughly 26% to 75% smaller per record:

What this comparison is. It compares the size of one portable artifact against an illustrative log record. The 100–300 byte range is a representative convention, not a measurement of any specific customer system, and the percentages are arithmetic on those illustrative figures.

What this comparison is not. It is not a comparison of equivalent capability, and not a total-cost comparison. A log record contains its own content; an H33-74 attestation commits to evidence that is retained separately, and the post-quantum signatures that make it checkable are carried alongside it — a single ML-DSA-65 signature is 3,309 bytes, far larger than the attestation itself. A system that retains the full evidence package and signature set stores considerably more than 74 bytes per event. Conventional logs and cryptographic attestations also serve different purposes: a log is a record an operator asks you to trust, while an attestation is evidence a third party can independently verify without trusting the operator or H33.

What would make it a cost claim. A defensible cost or efficiency claim requires a workload-level measurement that counts signatures, storage, retention, computation, transmission and verification together, on a stated configuration. H33 publishes no such measurement today, and therefore makes no total-cost claim. What is measured and reproducible is published with its methodology: ML-DSA-65 sizes, latencies and throughput, the on-chain footprint analysis, and the full benchmark suite.

The byte-exact wire format → · Receipt specification →

What proves it

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

How anyone verifies it — with H33 not in the loop

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

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

What it produces

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. Issue and verify →

Every H33-74 receipt contains a cryptographically bound H33-PQ-Time temporal proof. H33-74 cannot exist without it: each receipt binds a governed, bounded, replayable temporal proof from H33-PQ-Time — the single temporal authority proving when, in what causal order, within what bounded uncertainty, and with what replay/fork guarantees an event occurred. H33-PQ-Time is independently reusable infrastructure — H33-74 is one consumer; it consumes temporal truth, it does not originate time. See how time is proven →

Where it anchors — portability, not migration

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.

One receipt, three chains, zero migration →

Next step

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

Deep reference

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)