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 Solana. It expresses the H33-74 primitive for the Solana anchor surface; it does not add a new capability.
What you are reading. "H33-74 evidence anchored on Solana" is the H33-74 primitive — the portable 74-byte post-quantum proof produced and owned by H33-74 — expressed on Solana as its anchoring substrate. H33-74 is the proof primitive. Solana 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 Solana transaction that commits to a receipt's cryptographic identity (or to a batched commitment covering many receipts). The anchor lives in Solana's canonical ledger and is independently verifiable via any Solana block explorer.
H33-74 anchors to Solana via memo-instruction commitments and program-controlled anchor accounts. Receipts can be anchored individually for low-latency notarization or batched for cost efficiency.
What it does not contain: sensitive payload data. The receipt's content lives off-chain. The anchor only commits to its existence and identity.
Solana is the right anchor for high-volume operational evidence (millions of receipts per day), when sub-minute notarization latency is required, and when the operator can tolerate Solana's finality model in exchange for throughput and cost. Especially appropriate for AI decision systems, fraud-scoring pipelines, and compliance engines producing high-frequency receipts.
A receipt anchored on Solana 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 Solana 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 Solana.
A third-party verifier needs the H33-74 receipt, the Solana 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.
Solana is not always the right anchor. Another chain may be a better fit when you need the deepest decade-scale settlement assurance, when your evidence must live inside an EVM contract ecosystem, or when your compliance posture favors a specific chain's finality model over raw throughput. Those are legitimate reasons to anchor on Bitcoin for maximal settlement assurance, Ethereum for EVM interoperability, Polygon or Arbitrum for EVM-compatible L2 economics, or Avalanche for its consensus properties 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 Solana can anchor to any of the others.
One Receipt. Multiple Chains. H33-74 Overview