H33 vs Blockchain
Blockchain stores audit data publicly. H33 keeps it private while anchoring integrity to a blockchain.
Buyers evaluating blockchain for audit trails, compliance evidence, or provenance often hit the same wall: the chain works because it is public, but their evidence cannot be public. H33 solves the wall by separating integrity (which goes on-chain) from evidence (which stays under customer control). This page is for buyers comparing "put it on a blockchain" against "keep it private and anchor a commitment."
What blockchain provides
Public blockchains (Bitcoin, Ethereum, Avalanche, Cosmos, Solana, others) provide immutability, public verifiability, time binding (block timestamps), vendor independence, and decentralized consensus. These properties make blockchain attractive for evidence anchoring. The benefit is real. Buyers who consider putting their evidence on a blockchain are responding to a real shortcoming of internal systems.
What blockchain costs
Public blockchains achieve their properties by being public. Anything written to the chain is visible to anyone. Anything visible can be read by competitors, read by adversaries, read by regulators who would not otherwise have access, subject to data residency challenges, subject to GDPR Article 17 (right to be forgotten) compliance issues, subject to disclosure requirements that exceed the original scope. For most institutional evidence, this is unacceptable. AI decisions reference data that cannot be published. Insurance claims reference PII. Healthcare audit trails reference PHI. Regulatory submissions reference confidential business information. Federal evidence may be classified.
How H33 separates integrity from evidence
The H33 architecture treats integrity and evidence as separate concerns. Integrity — the proof that the evidence exists and has not been modified — is anchored to a public blockchain. The 32-byte commitment of the bundle is published as transaction calldata. The chain's block timestamp provides time binding. Anyone with a node can verify the anchor. Evidence — the underlying bundle with its eight EC objects, sidecars, and signatures — stays off-chain, under customer control. The bundle never touches the public ledger. The bundle's contents are not visible to anyone the customer does not share them with. The split provides blockchain's integrity benefits without blockchain's publicity cost.
Side-by-side
| Dimension | Generic Blockchain Audit Trail | H33 |
|---|---|---|
| Evidence storage | On-chain (public or permissioned) | Off-chain, under customer control |
| Integrity proof | The chain itself | 32-byte commitment anchored to chain |
| What's public | Everything stored on-chain | Only the 32-byte commitment |
| Confidentiality | Limited to permissioned chains or encryption | Full — bundle never on-chain |
| GDPR right to be forgotten | Difficult — chain is immutable | Straightforward — customer controls bundle |
| Storage cost | Scales with evidence size | 32 bytes regardless of evidence size |
| Quantum resistance | Depends on chain | Three-family PQ at bundle level |
Use cases
AI decision evidence. An AI underwriting decision references applicant PII. Putting the bundle on a blockchain would expose the PII. H33 anchors a 32-byte commitment; the bundle stays under the carrier's control. Healthcare audit trail. Clinical decision support evidence references PHI. The bundle stays in the hospital's HIPAA-compliant infrastructure. The 32-byte commitment is anchored to Avalanche. Regulatory submission. A pharmaceutical company's FDA submission contains confidential business information. The submission stays in the company's secure infrastructure. The commitment is anchored. Federal AI evidence. A federal agency's AI decisions reference personal records subject to Privacy Act protections. The bundles stay in the agency's accredited infrastructure. The commitments are anchored.
Common questions
Do I need to choose between blockchain and H33?
No. H33 uses a blockchain (Avalanche today) for the anchor. The choice is whether to put the full evidence on the chain or only the commitment.
Why Avalanche specifically?
Avalanche C-Chain provides sub-second finality, EVM compatibility, low transaction cost, public auditability, and subnet flexibility.
Can I anchor to multiple chains?
Yes. The bundle's anchor structure supports multiple chain references for redundancy.
What happens if Avalanche evolves?
The bundle's anchor record captures the chain identifier, transaction hash, and block hash. Historical anchors remain queryable. Future bundles can be anchored to alternative chains.
What about quantum cryptanalysis of the blockchain itself?
The blockchain's security depends on the chain's signature scheme. H33's three-family PQ signatures on the bundle survive even if the chain's signatures become forgeable.
Related: Avalanche Evidence Anchoring · H33 vs Blockchain Audit Trails · Chain-Agnostic Privacy · Avalanche Privacy