Schedule DemoGet started
Pricing
Sign in
AVALANCHE PRIVACY

Institutional Privacy for Avalanche Subnets.

Related · tier-1 reading. For the integrity anchor that makes this verifiable, see Avalanche Evidence Anchoring.

Avalanche subnets are built for institutions. But every subnet position, C-Chain balance, cross-subnet transfer, and validator stake is publicly visible. H33 adds post-quantum privacy to the blockchain platform designed for institutional deployment.

Schedule Demo Privacy Layer Hub
Example HATS status: NO PLAINTEXT SUBNET EXPOSURE DETECTEDIllustration
DEFINITION

Avalanche privacy is the expression of the H33 Privacy Layer on Avalanche (C-Chain and subnets). It protects the privacy of your evidence, identity, and chain interaction while anchoring a portable attestation to Avalanche. The privacy mechanism is a combination of zero-knowledge proof (ZK — STARK, no reveal), selective disclosure, and data minimization; the portable evidence itself is produced by H33-74 (the 74-byte post-quantum attestation), and the verdict is rendered by Verification. Avalanche is the reference environment the evidence anchors to — a 32-byte commitment — never the producer of the proof.

Why this exists: Avalanche subnets are built for institutional deployment, yet every subnet position, C-Chain balance, cross-subnet transfer, and validator stake is publicly visible. Avalanche provides fast finality and subnet isolation — it provides no privacy and no post-quantum evidence. The Privacy Layer supplies both, without asking you to trust Avalanche with anything more than a hash.

An Avalanche subnet workflow, step by step

  1. A subnet operator, validator network or cross-subnet bridge discloses only what a check needs (data minimisation); subnet positions, cross-subnet transfers and validator stakes stay off the public record.
  2. H33 proves the claim with a zero-knowledge STARK proof, for example that a validator’s stake is sufficient, without revealing the stake.
  3. H33-74 produces the portable post-quantum attestation, and a 32-byte commitment is written to the Avalanche C-Chain, which supplies fast finality and the anchor, never the proof.
  4. A counterparty or auditor verifies the attestation against that C-Chain commitment and receives the verdict from Verification, seeing only what was selectively disclosed.
LIVE CHAIN DATA
Avalanche C-Chain -- current block height
Connecting to Avalanche...
EXPOSURE COMPARISON
What changes when H33 is in the path

Native Avalanche

  • × Visible subnet positions
  • × Visible C-Chain balances
  • × Visible cross-subnet transfers
  • × Visible validator stakes
  • × Visible institutional DeFi positions
  • × Visible token holdings
  • × Visible bridge transactions
  • × Visible governance participation

H33 Protected

  • ✓ Encrypted subnet workflow
  • ✓ Attested execution proof
  • ✓ Hidden cross-subnet metadata
  • ✓ Proof-only stake verification
  • ✓ 32-byte calldata commitment
  • ✓ Independent verification (not yet available in production)
  • ✓ Post-quantum attestation
  • ✓ Replay-grade evidence
ATTESTATION RECEIPT
What an attestation receipt contains
h33-74 attestation receipt
H33-74 ATTESTATION RECEIPT Receipt ID: h74_attest_... DAG Root: 0x... (depth: 4, nodes: 12) Proof Hash: 0x... (STARK, 128-bit PQ security) Replay Ref: replay://h33.ai/r/... Chain Anchor: Avalanche C-Chain -- block ... Commitment: 0x... (32 bytes in calldata) SIGNATURES: ML-DSA-65: <verdict> (3,309 bytes -- MLWE lattice) FALCON-512: <verdict> (666 bytes, padded encoding -- NTRU lattice) SLH-DSA-128f: <verdict> (17,088 bytes -- hash-based) VERIFICATION: <checks passed / total> HATS LEVEL: Level 1 Conformance CACHEE KEY: cachee://h33.ai/c/... Replay This Attestation --> Open the verifier repository -->
ATTESTATION PIPELINE
Five stages. 32 bytes on-chain.
01
Subnet Data
Encrypted inputs from subnet
-->
02
STARK Proof
Constraint satisfaction without reveal
-->
03
PQ Signatures
ML-DSA + FALCON + SLH-DSA triple sign
-->
04
Cachee Store
Full proof bundle persisted off-chain
-->
05
Avalanche Anchor
32-byte commitment on C-Chain
32 bytes on-chain. Full proof off-chain. Designed for three PQ families (full three-family production verification pending). Zero data revealed.
DISCLOSURE BOUNDARY
What crosses the attestation boundary

NOT REVEALED

  • × Subnet positions
  • × C-Chain balances
  • × Cross-subnet transfers
  • × Validator stakes
  • × Institutional DeFi
  • × Token holdings
  • × Bridge transactions
  • × Governance votes

ONLY REVEALED

  • ✓ Cryptographic validity
  • ✓ Compliance proof
  • ✓ Stake sufficiency
  • ✓ Attestation commitment
  • ✓ Verification status
  • ✓ Replay availability
  • ✓ PQ signature bundle
  • ✓ Chain anchor hash
MULTI-CHAIN WITNESSING
Anchored across:
Avalanche
|
Ethereum
|
Bitcoin
|
Solana
Every attestation is witnessed across multiple chains. Cross-chain continuity.

Replay This Attestation

Inspect lineage. Inspect proof. Inspect DAG. Verify signatures.

Built For
Institutions deploying Avalanche subnets.
Subnet Operators
Institutional DeFi
RWA Tokenization
Validator Networks
Cross-Subnet Bridges
Compliance Teams
EXPLORE
50 Live Systems 44 ZK Use Cases

Subnets were built for institutions. Now they have privacy.

32 bytes on-chain. Post-quantum attestation. Privacy for the institutional blockchain platform.

Schedule Demo

H33.ai, Inc. · Patents Pending · HATS Standard · Privacy Layer · H33-74

DECISION GUIDANCE
When to use Avalanche privacy — and when not to

When to use this

  • ✓ Use this when your institutional workflow already runs on an Avalanche subnet or the C-Chain and you need portable proof anchored there.
  • ✓ Use this when you want fast-finality EVM anchoring with a 32-byte commitment inside subnet isolation.
  • ✓ Use this when you must prove compliance and solvency to a regulator while revealing nothing to competitors.

When NOT to use this

  • × Do not use this when you need maximum settlement permanence — use Bitcoin privacy instead.
  • × Do not use this when your evidence naturally settles elsewhere — use Ethereum privacy, Arbitrum privacy, or Base privacy.
  • × Do not use this when the need is encrypted computation over data that never decrypts — that is a different mechanism (FHE); use FHE instead. Anchoring the result back to Avalanche still routes through this page.
BOUNDARY QUESTIONS
Exactly what Avalanche privacy is — and is not
  1. 1. What privacy property is provided?
    Confidentiality of your evidence, identity, and on-chain interaction: subnet positions, balances, transfers, and stakes stay hidden while a proof of validity and compliance is published.
  2. 2. What is specific to Avalanche?
    The reference environment: a C-Chain or subnet commitment (32 bytes), sub-second finality, and subnet isolation for institutions. The chain is where the evidence anchors — it is not the producer of the evidence.
  3. 3. What remains supplied by H33-74?
    The portable evidence itself. H33-74 produces the 74-byte post-quantum attestation that travels across every chain unchanged; Avalanche only stores its commitment.
  4. 4. Is the mechanism ZK, FHE, minimization, selective disclosure, or a combination?
    A combination: zero-knowledge STARK proof, selective disclosure, and data minimization. FHE (encrypted computation) is a distinct mechanism and is used only if encrypted compute is genuinely in the workflow — see FHE.
  5. 5. What does the chain itself NOT provide?
    Avalanche provides no privacy, no post-quantum signatures, and no verification logic for the attestation. It reaches finality on a 32-byte commitment — nothing more.
  6. 6. How is the evidence independently verified?
    Verification is designed to render the verdict (not yet available for production receipts).
  7. 7. When should another chain or mechanism be preferred?
    Prefer Bitcoin for maximum permanence; Ethereum, Arbitrum, or Base when settlement lives there; and FHE when the need is computing on data that never decrypts.
FAQ
Avalanche privacy — questions
Is Avalanche privacy the same as encrypted computation (FHE)?

No. Avalanche privacy is an expression of the Privacy Layer — it protects evidence, identity, and chain interaction using ZK, selective disclosure, and minimization. Encrypted computation over data that never decrypts is a separate mechanism (FHE), covered at /fhe/. The two share the word “privacy” but not the mechanism.

Does Avalanche produce the proof?

No. The proof is produced by H33-74 and its verdict is rendered by Verification. Avalanche is the reference environment the 32-byte commitment anchors to — it never generates or verifies the attestation.

When should I choose a different chain?

Choose Bitcoin privacy when permanence matters most, or Ethereum, Arbitrum, or Base privacy when your evidence naturally settles there. The same H33-74 attestation is portable across all of them.