Related · tier-1 reading. For the integrity anchor that makes this verifiable, see Avalanche Evidence Anchoring.
Anyone recording high-stakes operational evidence needs it to outlive the system that produced it. H33-74 is the primitive that produces and anchors that portable post-quantum evidence — this page shows H33-74 evidence anchored on Avalanche. It expresses the H33-74 primitive for the Avalanche anchor surface; it does not add a new capability.
What you are reading. "H33-74 evidence anchored on Avalanche" is the H33-74 primitive — the portable 74-byte post-quantum proof produced and owned by H33-74 — expressed on Avalanche as its anchoring substrate. H33-74 is the proof primitive. Avalanche is one interchangeable anchoring substrate beneath it. The chain notarizes when a commitment existed; it is never the source of the proof or the trust.
H33-74 anchors to Avalanche C-Chain via EIP-1559 calldata commitments. The commitment is embedded in the transaction calldata as a self-send (no value transfer) so any Avalanche node can index and verify the commitment.
What it does not contain: sensitive payload data. The receipt's content lives off-chain. The anchor only commits to its existence and identity.
Avalanche is the right anchor when sub-second notarization latency is required, when subnet-style deployment flexibility is needed in the future, and when the operator values Avalanche's specific consensus properties for institutional adoption. The C-Chain provides EVM-compatible anchoring with fast finality.
A receipt anchored on Avalanche can also be anchored on Bitcoin, Ethereum, Solana, Polygon zkEVM, Zcash, or any other chain H33-74 supports. The anchors are independent. Adding more anchors does not change the receipt. Removing one anchor (or having one chain become unavailable) does not invalidate the others.
If Avalanche ever becomes inappropriate for an operator's use case (regulatory, performance, security, cost), the operator adds an anchor on a different chain and continues operating. The historical evidence does not have to migrate, because it was never bound to Avalanche.
A third-party verifier needs the H33-74 receipt, the Avalanche anchor transaction (or its hash), and the open-source H33 verifier. From those inputs:
What differs between blockchains are their operational and integration characteristics. The H33-74 primitive and its cryptographic properties remain unchanged.
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.
Avalanche is not always the right anchor. Another chain may be a better fit when you want the deepest decade-scale settlement assurance, when anchoring should inherit security directly from Ethereum through a rollup, or when raw throughput and lowest cost at extreme volume matter most. Those are legitimate reasons to anchor on Bitcoin for maximal settlement assurance, Ethereum L1 directly, Polygon or Arbitrum for rollup-inherited L1 security, or Solana for throughput and cost instead. In every case the H33-74 receipt stays portable: the same proof moves to the chain that fits, unchanged.
The same receipts that anchor to Avalanche can anchor to any of the others.
One Receipt. Multiple Chains. H33-74 Overview