Learn · 08
Privacy and the shielded pool
An opt-in way to make private BNB transfers, what it hides, what it doesn't, and why it isn't ready for real money.
Checked against official docs on 2026-10-29
StatusNot production-ready. The official docs say the shielded pool is not yet audited and should not be treated as safe for real value.
What it is
A built-in, opt-in privacy feature. Normal transactions stay public and unaffected. If you choose to, you can move BNB into the pool, transfer it privately, and move it back out.
It uses zero-knowledge proofs, which let you prove a transfer is valid without revealing the details.
What stays private, and what doesn't
| Action | What others can see |
|---|---|
| Private transfer inside the pool | Sender, recipient, amount and asset are hidden. The fee can be public. |
| Deposit into the pool | Sender, amount and asset |
| Withdraw from the pool | Recipient, amount and asset |
| Network activity | IP address and timing are not hidden |
Under developmentNative BNB deposits, withdrawals, private transfers and atomic calls are implemented on the devnet. Token shielding, compliance hooks and proof aggregation are not implemented yet.
Current limits
- Native BNB only. No BEP-20 or ERC-20 tokens yet.
- Several planned items are not implemented yet, including token shielding and compliance hooks.
- A formal setup ceremony and an independent circuit audit are still to be done before mainnet.
Confirmed by official docsThe official FAQ answers "Is the shielded pool safe to use with real funds today?" with "Not yet."
Our analysis (unofficial)Treat any app or person offering "private New L1 transfers" today with caution. The feature is experimental on a devnet.