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 Arbitrum One. It expresses the H33-74 primitive for the Arbitrum One anchor surface; it does not add a new capability.
What you are reading. "H33-74 evidence anchored on Arbitrum One" is the H33-74 primitive — the portable 74-byte post-quantum proof produced and owned by H33-74 — expressed on Arbitrum as its anchoring substrate. H33-74 is the proof primitive. Arbitrum One 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 Arbitrum One via EIP-1559 calldata commitments. As an optimistic rollup, Arbitrum settlement assurance inherits from Ethereum L1 once the batch is posted to L1.
What it does not contain: sensitive payload data. The receipt's content lives off-chain. The anchor only commits to its existence and identity.
Arbitrum One 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 an optimistic rollup. Particularly appropriate for DeFi-adjacent and RWA use cases that need EVM interoperability without paying Ethereum mainnet costs.
A receipt anchored on Arbitrum One 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 Arbitrum One 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 Arbitrum One.
A third-party verifier needs the H33-74 receipt, the Arbitrum One 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.
Arbitrum One is not always the right anchor. Another chain may be a better fit when you want anchoring directly on Ethereum L1 without an optimistic-rollup challenge window, when you prefer a zk-rollup's proof-based settlement, when the deepest decade-scale settlement assurance matters most, or when raw throughput and lowest cost outweigh EVM compatibility. Those are legitimate reasons to anchor on Ethereum L1 directly, Polygon for a zk-rollup, 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 Arbitrum One can anchor to any of the others.
One Receipt. Multiple Chains. H33-74 Overview