What is Solana privacy?

Solana privacy is a chain-specific expression of the H33 Privacy Layer. It protects the privacy of on-chain evidence, identity, and program interaction on Solana while allowing compliance, identity, and collateral to be verified without possessing user data. Evidence is produced by H33-74 and anchored to Solana as a 32-byte PDA commitment; Solana is a reference environment, not the owner of the privacy property.

Does H33 use ZK or FHE for Solana privacy?

It uses 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.

What does compliance without custody mean?

It means a protocol can verify a user's compliance, identity, or collateral using a cryptographic attestation instead of storing the user's raw PII. The privacy property and the portable evidence are supplied by H33-74 and the Privacy Layer, not by Solana.

When should I use a different chain or mechanism?

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

Solana-Privacy by H33 — Compliance Without Custody

LIVE ATTESTATION

Solana Mainnet -- current anchor status

Connecting to Solana Mainnet...

EXPOSURE COMPARISON

What changes when H33 is in the path

Native Solana

× Visible wallet balances
× Visible token holdings
× Visible DeFi positions
× Visible transaction history
× Visible counterparties
× Visible program interactions
× Visible staking delegations
× Visible NFT ownership

H33 Protected

✓ Encrypted position workflow
✓ Attested execution proof
✓ Hidden wallet metadata
✓ Proof-only balance verification
✓ 32-byte PDA 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:   Solana Mainnet -- slot ...
Commitment:     0x... (32 bytes on-chain PDA)

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.

User Data

Encrypted inputs from wallet or protocol

-->

STARK Proof

Constraint satisfaction without reveal

-->

PQ Signatures

ML-DSA + FALCON + SLH-DSA triple sign

-->

Cachee Store

Full proof bundle persisted off-chain

-->

Solana PDA

32-byte commitment in program account

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

DISCLOSURE BOUNDARY

What crosses the attestation boundary

NOT REVEALED

× Wallet balance
× Token holdings
× DeFi positions
× Staking delegations
× Counterparty identity
× Program interactions
× NFT ownership
× Transaction history

ONLY REVEALED

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

MULTI-CHAIN WITNESSING

Anchored across:

Solana

Bitcoin

Ethereum

Avalanche

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

Institutions building on Solana at scale.

Wallet Providers

DeFi Protocols

Stablecoin Issuers

RWA Tokenization

Institutional Desks

Compliance Teams

Stop broadcasting your positions to the network.

32 bytes on-chain. Post-quantum attestation. Privacy for the fastest settlement layer in crypto.

Schedule Demo

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

WHAT THIS IS

Solana privacy, defined

Solana privacy is a chain-specific expression of the H33 Privacy Layer — it protects the privacy of on-chain evidence, user identity, and program interaction on Solana while still letting a protocol or regulator verify compliance, identity, and collateral without possessing the underlying data. The evidence is produced by H33-74 and anchored to Solana as a 32-byte PDA commitment; Solana is a reference environment the proof records against, never the owner or producer of the privacy property.

Why this exists: every wallet balance, token holding, and DeFi position on Solana is readable by anyone with an RPC endpoint, and compliance today means custodying user PII. This page exists to replace PII custody with cryptographic attestations — compliance without custody, facts provable without being visible. The mechanism is zero-knowledge (STARK) 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 a Solana protocol must verify users, transactions, or collateral without holding their data.
Use this when the evidence must anchor specifically to Solana as a PDA commitment.
Use this when a counterparty must re-verify your proof independently.

When NOT to use this

Do not use this when your activity lives on another chain — use Ethereum, Polygon, or Hyperliquid privacy instead.
Do not use this when you need computation over still-encrypted data — use FHE instead.
Do not use this to hide obligations from a regulator — it proves compliance, it does not conceal it.

BOUNDARY QUESTIONS

1. What privacy property is provided?

Wallet balances, token holdings, DeFi positions, staking delegations, counterparties, program interactions, and NFT ownership stay hidden, while cryptographic validity, compliance, and balance sufficiency remain provable. It is bounded confidentiality of evidence, not anonymity.

2. What is specific to Solana?

The reference environment: the commitment anchors to Solana as a 32-byte PDA within a program account, and the relevant exposure is RPC-readable account state. The 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. Solana supplies none of it.

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

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

5. What does Solana itself NOT provide?

Solana provides no account privacy, no selective-disclosure proof, no post-quantum attestation, and no portable independently-verifiable evidence. Native account state is public over any RPC.

6. How is the resulting evidence independently verified?

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

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

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