Security / Trust
Solflare Private Mode: What It Hides and What Anyone Can Still See
Solflare Private Mode hides token amounts on Solana, but senders, recipients, deposits and withdrawals stay public. What that changes when you check a token.
On 15 November 2026 Solflare switched on Private Mode: a second balance inside the wallet whose contents don't show on a block explorer. It runs on Solana Privacy Rings, a protocol Helius put on mainnet five days earlier.
We read the protocol's accounts on mainnet and ran it on devnet. This post covers what Private Mode hides, what stays public, and one thing we think matters most to anyone who checks tokens before buying: a holder list can no longer tell you where all of the supply is.
What is hidden and what is public
Solflare's own page is direct about it: "A private balance is privacy for amounts, not anonymity."
| Hidden | Public | |
|---|---|---|
| Your private balance | Which tokens, and how much | That your address has a private wallet |
| A private payment | The token and the amount | Sender, recipient and time |
| Moving funds in | Nothing | Wallet, token and amount |
| Moving funds out | Nothing | Wallet, token and amount |
Three limits apply today, all from Solflare's FAQ. Private payments only reach other Solflare users who have set up Private Mode; pay anyone else and the wallet warns you, then sends an ordinary public transfer. Swaps, staking and dApps still use the public balance, so funds have to come back out before they can be traded. And the cost is listed as a "privacy + network fee" with no figure.
On that last point we can add something. The protocol's own account on mainnet sets a fee of 5,000 lamports for each input a private payment spends, which is the size of a normal Solana transaction fee. That is the protocol's charge as of 16 November. Whether Solflare adds anything on top, we couldn't tell from outside the wallet.
Where the tokens go
A private balance isn't stored in your wallet's token account. When you move funds in, the tokens go to a vault that the privacy program controls, and the program keeps an encrypted note of what you own. There is one vault per token, and every vault has the same owner:
CaM8DbtJ2mSecgaHYo9xeT7VSKq7AnaqEUm5p7e5LW4a
Because the vaults are ordinary token accounts, anyone can read their totals. On 16 November the mainnet vaults held about 186 SOL, 36,108 USDC and 427,314 BONK, with small amounts of USDT, ORE and JUP. PUMP had no vault at all yet. These are early numbers for a protocol that is six days old.
So the total held privately is public for every token. What you can't read is how that total splits between wallets.
We moved 30% of a token into a private balance
To see what a holder list makes of this, we made a token on devnet with a supply of 1,000,000 and deposited 300,000 from the only wallet that held it.
Mint: ENDqp9P7uPaqwZjqcfZxU7JJaVXxGYRhU7XjrQxye8u1 (devnet)
It took one transaction and one signature, and cost 0.0024 SOL, most of it rent for the new vault. The vault didn't exist before: the first deposit created it, with no approval from anyone. Afterwards the token's holders read like this:
- Our wallet: 700,000
- An account owned by
CaM8…LW4a: 300,000
Nothing on-chain says the second row is ours. Had a hundred other wallets deposited as well, they would all be inside that same row.
What this changes when you check a token
Most pre-buy checks lean on the holder list. How much do the top wallets hold? Does the deployer still have a bag? Did a cluster of linked wallets buy at launch? Each of those reads token accounts, and a private balance takes tokens out of the owner's token account without a sale.
That creates a specific blind spot. A deployer who deposits their allocation shows up as holding nothing. A tool that sorts holders into wallets and program-owned addresses will file the vault under programs, next to liquidity pools and locks, where it looks harmless. We know because our own Token Inspector did this until today: it would have reported the vault's share under "pools".
We changed that in three places:
- The Solana Token Inspector marks the vault row as "Private balances" and scores its share of supply on its own line. Past 4% it costs points, and from 20% it counts as a high-severity finding. We score it below a single wallet holding the same share, because unknown owners aren't proof of one owner.
- The Holder Snapshot labels the row and states how many tokens sit in private balances. If you build an airdrop list from a snapshot, the wallets behind those tokens won't be on it.
- The Telegram bot uses the same score, so it reports the same line.
The share of supply in private balances is small for every token we looked at. It's still worth a glance on a new token, where a single deposit can be a third of the supply, as ours was.
What a private balance doesn't hide
It would be a mistake to treat Private Mode as a cloak. Quite a lot stays readable.
Deposits and withdrawals are public in full. If a deployer moves 20% of supply into a private balance, the deposit shows the wallet, the token and the amount, and so does the withdrawal later. In Solflare today, tokens have to return to the public balance before they can be swapped, so a sale still has to surface first. Helius says private swaps can be built on the protocol, so that may not hold for long.
Counterparties are public too. A private payment shows who paid whom, so the funding links that tie wallets together are still there. Only the size is missing, and sometimes not even that: someone who deposits 1,000 USDC, makes one private payment, and whose recipient then withdraws 1,000 USDC hasn't hidden much.
Having a private wallet is itself visible. Setting one up writes a record to a public registry (it cost us 0.0012 SOL on devnet), and anyone can look up whether an address has one.
One signature you should never give a website
A private wallet has extra keys for encrypting and decrypting its balance. Helius's wallet guide describes deriving them from a single signature over a fixed message, and warns that whoever holds that signature can decrypt the wallet's private transactions. The message contains this text:
TSPP/derive/v1
We checked the published SDK and it behaves as described: the same wallet signing that message always produces the same keys. If a website ever asks you to sign a message with that string in it, refuse. Only your own wallet app should ever produce that signature.
Is it safe to use?
Your funds stay under your own keys, and every private payment still needs your signature. The open question is the code's age. Helius says three firms have audited the programs and circuits and that formal verification should finish by the end of 2026. Solflare's page says the audit results are still to be published. Both can be true, but until the reports are out we would keep private balances to amounts we could afford to have stuck.
Private Mode solves a real problem. Paying a contractor shouldn't publish your treasury, and a founder with a public address shouldn't have every transfer read by strangers. For token buyers it adds one more line to check. The Token Inspector is free and needs no wallet, and it now shows that line for any mint you paste.