What is Zcash privacy in the H33 Privacy Layer?

It is a chain-specific expression of the H33 Privacy Layer that anchors a portable, post-quantum, independently-verifiable attestation to Zcash and adds a provable compliance path. It does not replace or own Zcash's native shielded-pool privacy; Zcash's Groth16 shielded transactions are the protocol's own primitive. H33 adds a separate attestation layer anchored to Zcash as a 32-byte memo-field commitment.

Does H33 use ZK or FHE for Zcash privacy?

It uses post-quantum zero-knowledge (STARK) proofs together with data minimization and selective disclosure, plus H33-74 post-quantum attestation. It does not use FHE. If you need computation over data that stays encrypted, use H33 FHE at /fhe/ instead.

When should I use a different chain or mechanism?

Use another chain's privacy page (Solana, Polygon, Hyperliquid, Optimism) if your activity is not on Zcash, and use FHE when you must compute over still-encrypted data rather than attest facts about it.

Zcash Privacy -- Privacy Without Quantum Expiration

Q: Does H33 replace Zcash's shielded privacy?

No. Zcash's shielded pool still provides its own transaction confidentiality. H33 adds a post-quantum attestation and a selective-disclosure compliance proof alongside it, addressing the quantum-vulnerability of Groth16 proofs and the absence of a built-in compliance mechanism.

LIVE ATTESTATION

Zcash Mainnet -- current anchor status

Connecting to Zcash...

EXPOSURE COMPARISON

What changes when H33 is in the path

Native Zcash (Groth16)

× Shielded pool metadata leakage
× Viewing key exposure risk
× Transaction graph analysis
× Timing correlation attacks
× Amount correlation attacks
× Network-level analysis
× Quantum-retroactive decryption
× No compliance mechanism

H33 Protected

✓ Post-quantum shielded workflow
✓ Attested execution proof
✓ Hidden pool metadata
✓ Proof-only compliance verification
✓ 32-byte memo commitment
✓ Independent verification
✓ STARK-based attestation
✓ Replay-grade evidence

ATTESTATION RECEIPT

What a verified attestation looks like

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:   Zcash Mainnet -- block ...
Commitment:     0x... (32 bytes in memo field)

SIGNATURES:
  ML-DSA-65:    VALID (3,309 bytes -- MLWE lattice)
  FALCON-512:   VALID (666 bytes -- NTRU lattice)
  SLH-DSA-128f: VALID (17,088 bytes -- hash-based)

VERIFICATION:   ALL CHECKS PASSED (20/20)
HATS LEVEL:     Level 1 Conformance
CACHEE KEY:     cachee://h33.ai/c/...

Replay This Attestation -->    Verify Independently -->

ATTESTATION PIPELINE

Five stages. 32 bytes on-chain.

Shielded Tx

Encrypted inputs from shielded pool

-->

STARK Proof

Post-quantum constraint satisfaction

-->

PQ Signatures

ML-DSA + FALCON + SLH-DSA triple sign

-->

Cachee Store

Full proof bundle persisted off-chain

-->

Memo Anchor

32-byte commitment in memo field

32 bytes on-chain. Full proof off-chain. Three PQ families. Zero data revealed.

DISCLOSURE BOUNDARY

What crosses the attestation boundary

NOT REVEALED

× Shielded amounts
× Sender identity
× Receiver identity
× Transaction graph
× Viewing keys
× Pool membership
× Timing patterns
× Amount correlations

ONLY REVEALED

✓ Cryptographic validity
✓ Compliance proof
✓ PQ attestation
✓ Attestation commitment
✓ Verification status
✓ Replay availability
✓ PQ signature bundle
✓ Chain anchor hash

MULTI-CHAIN WITNESSING

Anchored across:

Zcash

Bitcoin

Ethereum

Solana

Every attestation is witnessed across multiple chains. Cross-chain continuity.

Replay This Attestation

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

Replay Proof View DAG Verify Signatures HATS Verifier

Built For

Privacy-first users who need quantum resilience.

Privacy Advocates

Institutional Users

Compliance Teams

Zcash Ecosystem

Cross-Chain Bridges

Regulatory Bodies

WHAT THIS IS

Zcash privacy (H33 expression), defined

Zcash privacy here is a chain-specific expression of the H33 Privacy Layer — it anchors portable, post-quantum, independently-verifiable evidence to Zcash and adds a provable compliance path that Zcash's protocol does not offer. It does not replace or own Zcash's native shielded-pool privacy: Zcash's Groth16 shielded transactions are the protocol's own primitive, and H33 does not produce or govern them. H33 supplies a separate attestation layer that anchors to Zcash as a 32-byte memo-field commitment; Zcash is a reference environment the proof records against.

Why this exists: Zcash shielded transactions rely on Groth16 over BN254, which is quantum-vulnerable — a future cryptographically relevant quantum computer could break those proofs retroactively, and Zcash offers no built-in compliance mechanism. This page exists to add post-quantum attestation and a selective-disclosure compliance proof alongside Zcash's shielded privacy, not in place of it. The mechanism is zero-knowledge (STARK, post-quantum) proof plus selective disclosure and H33-74 attestation — distinct from encrypted compute (FHE), which keeps data encrypted while it is being processed.

When to use this

Use this when you want a post-quantum, portable compliance attestation anchored to Zcash activity.
Use this when you need a provable compliance path that Zcash's shielded protocol does not itself provide.
Use this when a counterparty must re-verify your proof independently.

When NOT to use this

Do not use this expecting it to replace Zcash's shielded privacy — Zcash's own protocol still provides that; H33 adds an attestation layer on top.
Do not use this when your activity is on another chain — use Solana, Polygon, or Hyperliquid privacy instead.
Do not use this when you need computation over still-encrypted data — use FHE instead.

BOUNDARY QUESTIONS

1. What privacy property is provided?

H33 adds a post-quantum, independently-verifiable compliance attestation whose inputs (shielded amounts, sender/receiver, transaction graph, viewing keys) stay hidden while validity and compliance remain provable. Zcash's shielded pool provides the underlying transaction confidentiality; H33 does not supersede it.

2. What is specific to Zcash?

The reference environment: Zcash has native shielded/ZK privacy via Groth16, which is quantum-vulnerable and has no built-in compliance path. The H33 commitment anchors to a Zcash memo field. The attestation primitive itself is unchanged from every other chain.

3. What remains supplied by H33-74?

The 74-byte post-quantum attestation, three-family PQ signature bundle, replay reference, and cross-chain portability are all supplied by H33-74. Zcash supplies its own shielded privacy but none of the H33 attestation layer.

4. Is the mechanism ZK, FHE, minimization, selective disclosure, or a combination?

A combination of zero-knowledge (post-quantum STARK) proof, data minimization (32 bytes on-chain), and selective disclosure. It does not use FHE — for encrypted compute see /fhe/.

5. What does Zcash itself NOT provide?

Zcash provides shielded privacy but no post-quantum resilience for those proofs, no built-in compliance mechanism, and no portable H33-74 attestation independently verifiable off-chain. Those are what this expression adds.

6. How is the resulting evidence independently verified?

Through H33 Verification — replay the STARK proof, re-check the three PQ signatures, and confirm the memo-field commitment with the open-source verifier. No trust in H33 or Zcash is required.

7. When should another chain or privacy mechanism be preferred?

Prefer another chain page when the activity is not on Zcash, and prefer FHE when the requirement is computing over data that must stay encrypted rather than attesting facts about it.

Privacy without an expiration date.

32 bytes on-chain. Post-quantum attestation. Privacy that survives the quantum transition.

Schedule Demo

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