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 Zcash. It expresses the H33-74 primitive for the Zcash anchor surface; it does not add a new capability.
Each anchor is a Zcash transaction that commits to a receipt's cryptographic identity (or to a batched commitment covering many receipts). The anchor lives in Zcash's canonical ledger and is independently verifiable via any Zcash block explorer.
H33-74 anchors to Zcash by embedding the receipt's commitment in shielded transaction memos. The anchor record itself can be shielded so that the existence of the anchor is not visible to third parties without the viewing key. Selective disclosure allows specific parties (regulators, auditors, counterparties) to verify the anchor while keeping it opaque to others.
What it does not contain: sensitive payload data. The receipt's content lives off-chain. The anchor only commits to its existence and identity.
Zcash is the right anchor when the existence of the anchor record itself needs to remain confidential, when regulated parties need selective disclosure rather than universal transparency, and when the operator wants privacy-preserving notarization for sensitive operational evidence. Particularly appropriate for compliance evidence in regulated industries where the fact that a compliance event occurred is itself sensitive.
A receipt anchored on Zcash 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 Zcash 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 Zcash.
What differs between blockchains are their operational and integration characteristics. The H33-74 primitive and its cryptographic properties remain unchanged. Confidentiality of the anchor record, confirmation time, and fee level differ between Zcash and, say, Bitcoin — the 32-byte commitment, the three post-quantum signatures, and the verification steps 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. A receipt first anchored on Zcash and later anchored on Ethereum or Solana is the same receipt, proven by the same signatures, checked by the same open verifier.
A third-party verifier needs the H33-74 receipt, the Zcash 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.
H33-74 is the portable proof primitive — a 74-byte post-quantum attestation. Zcash is one interchangeable anchoring substrate that H33-74 evidence can be recorded on, distinguished by its shielded, privacy-preserving notarization. The chain is the transport layer for a notarization; the proof itself is produced and carried by H33-74.
No. Anchoring writes a 32-byte commitment into a shielded memo and inherits a Zcash block timestamp. The cryptographic evidence — three independent post-quantum signatures over the receipt — is unchanged by the choice of chain. H33-74 anchors its evidence to Zcash; the proof and verification come from H33-74's cryptography, not from Zcash.
From H33-74. Zcash contributes one independent, optionally shielded existence-time notarization. Authenticity and unforgeability come from H33-74's signatures and the independent verifier, which behave identically on every chain.
Yes. The same receipt anchors on Bitcoin, Ethereum, Solana, or any supported chain. 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.
Zcash's shielded memos keep the existence of the anchor record confidential, with selective disclosure through viewing keys — a property of the Zcash anchor surface. The receipt's payload is already off-chain on every chain; Zcash additionally conceals that an anchor exists. The H33-74 primitive and its verification are unchanged.
Legitimate reasons exist to prefer a different chain: Bitcoin for the most conservative and publicly transparent settlement, an EVM L2 like Base or Optimism where Ethereum tooling is required, Solana or Hedera for higher throughput and low fixed fees, Cosmos where a sovereign app-specific zone is needed. Zcash is not always the best fit — its value is confidential notarization — but whichever chain you choose, the H33-74 primitive stays portable across all of them, so the choice is an operational one, not a change to the proof.
The same receipts that anchor to Zcash can anchor to any of the others.
One Receipt. Multiple Chains. H33-74 Overview