Publicly verifiable integrity that survives infrastructure changes. The chains are examples. The integrity layer is the concept.
H33 is chain-agnostic. No blockchain occupies a privileged conceptual slot. Bitcoin, Solana, Avalanche, Polygon, Zcash, Ethereum, Arbitrum, Base, Optimism, Cosmos, and Hedera are implementations of the same idea.
Verify a Bundle → See the ArchitectureThe public integrity layer is the chain-agnostic property that a portable H33-74 evidence artifact can anchor to a public blockchain for a tamper-evident, publicly checkable timestamp — while the artifact stays verifiable independent of which chain anchored it, or whether that chain still exists. Why it exists: when integrity is bound to a specific chain, vendor, cloud, or implementation, the evidence dies when the infrastructure changes. H33 inverts that — the artifact is the asset; the chain is the proof surface, not the proof.
Boundary: H33-74 produces the artifact; each chain is a reference environment the artifact anchors to — it does not own or produce the evidence. Anchoring is not the verdict: whether an artifact is valid and canonical is rendered by H33 Verification, which re-checks it offline. Anchoring is not operational monitoring — recording and watching evidence over time is HATS. Anchoring is not governance: approving who may act is Agent-008.
Portable evidence survives chain migration, cloud migration, vendor replacement, software replacement, and model replacement. The evidence is the asset. Everything else is implementation.
Chains are implementation layers. Integrity is a thesis layer. Mixing them is what produces lock-in.
An H33-74 attestation is verifiable independent of which chain anchored it — or whether that chain still exists.
Every chain we support is interchangeable from the integrity layer's perspective. None is privileged.
Anyone can verify an H33 artifact without contacting H33, without depending on a particular cloud, and without trusting any single chain to remain operational.
Each chain is a proof surface. None is a thesis surface. Pick the chain that matches your operational requirements — the artifact remains identical and independently verifiable across all of them.
The Public Integrity Layer is one of eight Tier-1 thesis concepts. It explains why the H33 substrate exists. Implementation lives in the lower tiers.
The chain is an operational choice, not an architectural dependency. Because the artifact re-verifies offline, anchoring is something you attach for a public timestamp, never something the evidence depends on.
When to use this: use it when you need a portable H33-74 artifact to carry a public, tamper-evident timestamp that survives chain migration, vendor replacement, and infrastructure change. When not to use this: do not use anchoring when you need the verdict on whether the artifact is valid and canonical — use Verification instead; do not use it when you need to record and watch evidence over time — use HATS instead; and do not use it to approve who may act — use Agent-008 instead. The chain supplies only a timestamp and ordering.
Choose Bitcoin (via Taproot) for the most widely recognized public timestamp on high-value evidence. Slower finality, higher cost.
Choose Ethereum when you want the largest verifiable-settlement ecosystem and programmable on-chain verification.
Base, Arbitrum, Optimism, Polygon, Avalanche, or Solana give fast finality at low cost — best for high-volume evidence.
The artifact still re-verifies offline against schema and hash. An internal store or regulator ledger can serve as the anchor. Anchoring is optional.