ETHEREUM PRIVACY

Compliant Privacy for Ethereum.

Q: Is Ethereum privacy the same as encrypted computation (FHE)?

No. Ethereum privacy is an expression of the H33 Privacy Layer that protects evidence, identity, and chain interaction using zero-knowledge proofs, selective disclosure, and data minimization. Encrypted computation over data that never decrypts is a separate mechanism (FHE). The two share the word privacy but not the mechanism.

Q: Does Ethereum produce the proof?

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

Q: When should I choose a different chain for privacy?

Choose Bitcoin privacy when settlement permanence matters most, or Arbitrum, Base, or Avalanche privacy when your evidence lives there and you want lower fees. The same H33-74 attestation is portable across all supported chains.

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

Tornado Cash failed because it had no compliance layer. H33 provides one. Every token balance, every DeFi position, every swap is visible on-chain. H33 adds post-quantum privacy with per-transaction compliance attestation.

Schedule Demo Privacy Layer Hub

DEFINITION

Ethereum privacy is the expression of the H33 Privacy Layer on Ethereum L1 (and every L2 that settles to it). It protects the privacy of your evidence, identity, and chain interaction while anchoring a portable, independently verifiable attestation to Ethereum. 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. Ethereum is the reference environment the evidence anchors to — a 32-byte commitment in calldata — never the producer of the proof.

Why this exists: Tornado Cash proved that privacy without a compliance layer becomes a regulatory dead end. On Ethereum every token balance, DeFi position, and swap is public, yet the chain provides no privacy and no post-quantum evidence. The Privacy Layer supplies both — compliance to the regulator and privacy to the user — without asking you to trust Ethereum with anything more than a hash.

LIVE ON ETHEREUM MAINNET

Tokenize the World — anchored 2026-05-27

A $50M reference treasury transfer’s full institutional state — every encrypted policy gate, every authority transition, every signature — collapsed to one 32-byte SHA3-256 canonical fact, then anchored to Ethereum mainnet. Not compressed. Fully post-quantum attested.

CONFIRMED · ETHEREUM MAINNET

block 25,184,389 · 2026-05-27 04:49 UTC

Tx Hash:0x38c62e5825…ab0e593f ↗

Calldata:0x5c741f1ce74a759d7b142f08c5f4dae3954f8174708bce1ad7afb7aef996f770

Calldata Size:32 bytes · SHA3-256 · not compressed

SHA3-256 Of:fraud-bundle.json (6,080 bytes)

Cost To Anchor:0.000047 ETH (22,280 gas × 2.108 gwei)

Signer:0xF84E…AA83 ↗

PQ Families:ML-DSA-65 · FALCON-512 · SLH-DSA-128f

      The full bundle is independently verifiable. Run the open-source verifier and re-derive this exact 32-byte commitment yourself.

      Watch the replay →  ·  Public verifier ↗  ·  Receipt JSON

EXPOSURE COMPARISON

What changes when H33 is in the path

Native Ethereum

× Visible token balances
× Visible DeFi positions
× Visible swap history
× Visible lending positions
× Visible NFT ownership
× Visible ENS resolution
× Visible gas usage patterns
× Visible MEV vulnerability

H33 Protected

✓ Encrypted transaction workflow
✓ Attested execution proof
✓ Hidden position metadata
✓ Proof-only compliance verification
✓ 32-byte calldata commitment
✓ Independent verification
✓ Post-quantum 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:   Ethereum Mainnet -- block ...
Commitment:     0x... (32 bytes in calldata)

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.

Transaction

Encrypted inputs from DeFi protocol

-->

STARK Proof

Constraint satisfaction without reveal

-->

PQ Signatures

ML-DSA + FALCON + SLH-DSA triple sign

-->

Cachee Store

Full proof bundle persisted off-chain

-->

EVM Calldata

32-byte commitment on Ethereum L1

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

DISCLOSURE BOUNDARY

What crosses the attestation boundary

NOT REVEALED

× Token balances
× DeFi positions
× Swap history
× Lending positions
× NFT ownership
× ENS identity
× Gas patterns
× MEV exposure

ONLY REVEALED

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

DECISION GUIDANCE

When to use Ethereum privacy — and when not to

When to use this

✓ Use this when your DeFi positions, stablecoin flows, or RWA tokenization settle on Ethereum L1 and you need portable proof anchored there.
✓ Use this when you want the deepest EVM settlement assurance with a 32-byte calldata commitment and an on-chain footprint you can point a regulator at.
✓ Use this when you must prove compliance and solvency while revealing nothing about balances or positions.

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 lives on an L2 or subnet and you want lower fees there — use Arbitrum privacy, Base privacy, or Avalanche 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 Ethereum still routes through this page.

BOUNDARY QUESTIONS

Exactly what Ethereum privacy is — and is not

1. What privacy property is provided?
Confidentiality of your evidence, identity, and on-chain interaction: token balances, DeFi positions, swap history, and counterparties stay hidden while a proof of validity and compliance is published.
2. What is specific to Ethereum?
The reference environment: an Ethereum L1 calldata commitment (32 bytes), the deepest EVM settlement layer, and the base every L2 inherits security from. The chain is where the evidence anchors — it is not the producer of the evidence.
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; Ethereum only stores its commitment.
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. What does the chain itself NOT provide?
Ethereum provides no privacy, no post-quantum signatures, and no verification logic for the attestation — its own ECDSA is not quantum-resistant. It orders and settles a 32-byte commitment — nothing more.
6. How is the evidence independently verified?
Verification renders the verdict: re-derive the exact 32-byte commitment from the published bundle and check the three post-quantum signature families offline with the open-source verifier — no trust in H33 or Ethereum required.
7. When should another chain or mechanism be preferred?
Prefer Bitcoin for maximum permanence; Arbitrum, Base, or Avalanche for lower-fee anchoring where your evidence lives; and FHE when the need is computing on data that never decrypts.

FAQ

Ethereum privacy — questions

Is Ethereum privacy the same as encrypted computation (FHE)?

No. Ethereum 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 Ethereum produce the proof?

No. The proof is produced by H33-74 and its verdict is rendered by Verification. Ethereum 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 Arbitrum, Base, or Avalanche privacy when your evidence lives there and you want lower fees. The same H33-74 attestation is portable across all of them.