Token-2022 Confidential Transfers Guide — Private Transactions on Solana

Confidential transfers are a Token-2022 extension that hides transfer amounts using zero-knowledge proofs. The sender, recipient, and amount are recorded on-chain, but the amount is encrypted — only the sender and recipient can see how many tokens were transferred. Validators can still verify that the transaction is valid without seeing the actual amount.

How Confidential Transfers Work

Standard Transfers (Visible)

With standard SPL or Token-2022 tokens, every transfer is fully public:

• Anyone can see the sender address
• Anyone can see the recipient address
• Anyone can see the exact amount transferred
• Block explorers display all details

Confidential Transfers (Encrypted Amounts)

With the confidential transfer extension enabled:

• The sender address is visible
• The recipient address is visible
• The transfer amount is encrypted on-chain
• Only the sender and recipient can decrypt the amount
• Validators verify the transaction using zero-knowledge proofs

This means anyone can see that a transfer happened between two addresses, but they cannot see how much was transferred.

Zero-Knowledge Proofs Explained

Confidential transfers use zero-knowledge proofs to ensure transaction validity without revealing amounts. The proof demonstrates:

1. The sender has enough tokens — The encrypted balance is sufficient for the transfer
2. No tokens are created or destroyed — The encrypted debit equals the encrypted credit
3. The amount is non-negative — You cannot send negative amounts (which would effectively create tokens)

The validator checks these proofs mathematically without ever seeing the actual numbers.

Use Cases for Confidential Transfers

Business Payments

Companies may not want competitors to see their transaction amounts. Confidential transfers keep payment values private while maintaining on-chain settlement.

Payroll

Paying employees or contractors in tokens without publicly revealing salaries.

OTC Trades

Large over-the-counter trades where parties do not want the market to see the transaction size, which could cause price impact.

Privacy-Sensitive Applications

Any application where transaction amounts should be private between the parties involved.

Compliance with Privacy Regulations

Some jurisdictions require financial privacy protections. Confidential transfers provide amount privacy while maintaining an auditable trail.

Technical Architecture

Encryption

Each token account with confidential transfers enabled has:

• Encrypted balance — The actual balance encrypted with the account owner's public key
• Pending balance — Incoming transfers that have not yet been applied
• Available balance — Decrypted balance available for transfers

Transfer Flow

1. Sender encrypts the transfer amount using the recipient's ElGamal public key
2. Sender generates a zero-knowledge proof demonstrating validity
3. Transaction submitted with encrypted amount and proof
4. Validator verifies the proof without decrypting the amount
5. Recipient's pending balance updated with the encrypted amount
6. Recipient applies pending balance by decrypting and adding to their available balance

Key Components

• ElGamal encryption — Homomorphic encryption scheme that allows mathematical operations on encrypted values
• Sigma proofs — Zero-knowledge proofs for balance validity
• Range proofs — Prove amounts are within valid ranges without revealing them

Creating a Confidential Transfer Token

Confidential transfers require the extension to be enabled at token creation time. This is an advanced feature that currently requires programmatic interaction with the Token-2022 program.

Prerequisites

• Solana CLI tools installed
• Understanding of Token-2022 program architecture
• SPL Token CLI or custom program integration

High-Level Steps

1. Create a Token-2022 mint with the ConfidentialTransferMint extension
2. Configure the mint with the auditor ElGamal public key (optional)
3. Create token accounts with confidential transfer capability
4. Generate ElGamal keypairs for each account holder
5. Deposit tokens from public balance to confidential balance
6. Transfer using the confidential transfer instruction
7. Apply pending balance on the recipient side

Auditor Key (Optional)

You can optionally set an auditor ElGamal public key during mint creation. The auditor can decrypt all transfer amounts for compliance purposes, while the public still cannot see amounts.

This is useful for:

• Regulatory compliance (auditors can verify all transactions)
• Internal accounting (company treasury can see all transfers)
• Tax reporting (designated authority can see amounts)

Current Limitations

Ecosystem Support

Confidential transfers are a newer extension with limited ecosystem support as of 2026:

• Wallets — Limited native support; most wallets show encrypted balances as unavailable
• DEXs — Most DEXs do not support confidential transfer tokens for trading
• Block explorers — Show encrypted amounts rather than actual values

Performance

Confidential transfers require more compute units than standard transfers due to proof generation and verification. This means:

• Slightly higher transaction fees
• Client-side proof generation takes a few seconds
• Not suitable for high-frequency micro-transactions

No Confidential Balances on Public View

While transfer amounts are encrypted, the existence of transfers is public. Sophisticated observers can still:

• Track that a transfer occurred between two addresses
• Observe timing patterns
• See the number of transactions (even if amounts are hidden)

Confidential Transfers vs Other Privacy Solutions

| Feature | Confidential Transfers | Tornado Cash (Ethereum) | Zcash | |---------|----------------------|------------------------|-------| | Blockchain | Solana | Ethereum | Zcash | | What's hidden | Transfer amounts | Sender/recipient/amount | Everything (shielded) | | Sender visible | Yes | No | No (shielded) | | Recipient visible | Yes | No | No (shielded) | | Compliance friendly | Yes (auditor key) | No | Partially | | Built-in standard | Yes (Token-2022) | Separate contract | Native protocol |

Confidential transfers are designed for compliance-friendly privacy — hiding amounts while maintaining transparent participant identity.

When NOT to Use Confidential Transfers

• Meme coins — Transparency is expected; hidden amounts would reduce trust
• Public governance — Voting amounts should be visible
• Standard DeFi — Most DeFi protocols require visible balances for proper functioning
• Tokens needing wide DEX support — Limited DEX compatibility

Getting Started

For most token projects, standard SPL tokens or basic Token-2022 tokens are the right choice. Confidential transfers are a specialized feature for projects with specific privacy requirements.

If you need a standard token, create one instantly at SolTokenCreator.io. For Token-2022 tokens with other extensions (transfer fees, non-transferable), use our Token-2022 Creator.

For confidential transfers specifically, consult the Solana Token-2022 documentation and consider working with a Solana development team familiar with the extension.

Related Guides

• Token-2022 Extensions Guide — All extensions explained
• SPL vs Token-2022 — Choose the right standard
• Transfer Fee Tutorial — Built-in tax tokens
• Token Security Best Practices — Secure your token
• Token-2022 Creator — Create Token-2022 tokens