Mint Once. Anchor Anywhere.
Verify Forever.

This is the operating model underneath every H33-74 deployment. Three operations, each independent, each playing one specific role.

Mint once

An H33-74 receipt is produced from the result of one bounded computation. The computation can be anything: an AI decision, a compliance determination, a governance vote, a transfer authorization, a KYC outcome, a FHE output, a tokenization action.

The receipt commits to the computation's result and signs it under three independent post-quantum families (ML-DSA-65, FALCON-512, SLH-DSA-128f). The signing happens once. The 74-byte receipt is fixed from that moment.

Anchor anywhere

Anchoring is the act of recording the receipt's existence to a public chain. It is optional, deferrable, and repeatable.

• Anchor immediately or anchor later.
• Anchor on one chain or anchor on multiple chains.
• Anchor individually or in batched commitments covering many receipts.
• Anchor on cheap chains for routine evidence and on expensive chains for high-value evidence.
• Anchor on whichever chain the verifying counterparty prefers.

None of these choices affect the receipt itself. The receipt was minted before anchoring and remains the same regardless of which chains hold notarizations.

Verify forever

Verification requires only the receipt and the verifier tooling. The verifier is open-source, runnable without H33 infrastructure, and architected to survive H33 itself. (This is documented in H33-74 whitepaper and in the H33 verifier project on GitHub.)

A receipt remains verifiable as long as:

• The 74-byte receipt content is preserved (the holder of record stores it).
• The public keys used to sign it are preserved (published in canonical registries).
• The verifier software is preserved (open-source, public, replicable).

None of those requirements depend on a specific chain. A receipt anchored on a chain that is later deprecated remains verifiable because the chain anchor was independent notarization, not the proof itself.

Why this matters

What differs between chains — and what never does

What differs between blockchains are their operational and integration characteristics. The H33-74 primitive and its cryptographic properties remain unchanged. Fees, finality latency, anchor method (Taproot, PDA, calldata) and availability vary chain to chain; the receipt, its three post-quantum signatures, and the verification model do not.

Migrating from one blockchain to another changes the anchoring substrate and deployment environment. It does not change the H33-74 primitive, the cryptographic evidence, or the verification model. That is why "anchor anywhere" is a routine operation and not a re-issuance.

What H33-74 does not do

H33-74 produces and anchors the portable proof primitive. It is deliberately narrow:

• It does not monitor systems or watch for control drift over time — that is HATS.
• It does not render the verdict on whether an attestation is valid — an independent verifier does that; see Verification.
• It does not govern agents or preserve decision authority — that is Agent-008.

H33-74 mints the receipt and lets you anchor it anywhere. Everything else is a separate, clearly-owned layer.

Concrete example: a five-year operation

A tokenized fund operates for five years on Ethereum. Every action produces an H33-74 receipt. Year one through year three, anchors go to Ethereum daily. Year three, the fund adds Bitcoin anchors weekly for high-value receipts. Year four, post-quantum considerations push the fund to add a third chain that uses PQ-secured consensus. Year five, the fund decides to migrate off Ethereum entirely.

Mint operations: unchanged. Receipts produced exactly the same way.

Anchor operations: evolved. Anchor set per receipt category shifted over time, additively. No anchor was retracted; new anchors were added.

Verify operations: unchanged. Every receipt produced in year one is still verifiable in year five using the same verifier with no migration needed.

Frequently asked

Related