Category · tier-1 reading. This page is one implementation of H33's chain-agnostic integrity thesis. For the concept that spans all 11 supported chains, see Public Integrity Layer.
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 Polygon zkEVM. It expresses the H33-74 primitive for the Polygon zkEVM anchor surface; it does not add a new capability.
What you are reading. "H33-74 evidence anchored on Polygon zkEVM" is the H33-74 primitive — the portable 74-byte post-quantum proof produced and owned by H33-74 — expressed on Polygon as its anchoring substrate. H33-74 is the proof primitive. Polygon zkEVM 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.
Each anchor is a Polygon zkEVM transaction that commits to a receipt's cryptographic identity (or to a batched commitment covering many receipts). The anchor lives in Polygon zkEVM's canonical ledger and is independently verifiable via any Polygon zkEVM block explorer.
H33-74 anchors to Polygon zkEVM mainnet via EIP-1559 transactions with the receipt's 32-byte commitment (or batched Merkle root) embedded in calldata. The receipt's identity is committed to L2, and once the L2 batch is proven and posted to Ethereum L1, the anchor inherits L1-grade security.
What it does not contain: sensitive payload data. The receipt's content lives off-chain. The anchor only commits to its existence and identity.
Polygon zkEVM is the right anchor when EVM-compatible tooling is needed, when L1-grade settlement assurance is required but L1 gas costs are not, and when the operator wants the security inheritance of a zk-rollup. Particularly appropriate for RWA and tokenization use cases that need EVM interoperability without paying Ethereum mainnet costs per anchor.
A receipt anchored on Polygon zkEVM 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 Polygon zkEVM 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 Polygon zkEVM.
A third-party verifier needs the H33-74 receipt, the Polygon zkEVM anchor transaction (or its hash), and the open-source H33 verifier. From those inputs:
None of those steps depends on H33's infrastructure. The verifier is open-source and the chain is public.
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.
Polygon zkEVM is not always the right anchor. Another chain may be a better fit when you want anchoring directly on Ethereum L1 rather than an L2 with proof-posting latency, when the deepest decade-scale settlement assurance matters most, or when raw throughput and lowest per-anchor cost outweigh EVM compatibility. Those are legitimate reasons to anchor on Ethereum L1 directly, Arbitrum for a different L2 model, Bitcoin for maximal settlement assurance, Solana for throughput and cost, or Avalanche for fast finality 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 Polygon zkEVM can anchor to any of the others.
One Receipt. Multiple Chains. H33-74 Overview