The shielded pool.
A zero-knowledge pool for BNB, built like Tornado Nova. You can shield, unshield and send privately on Move BNB. Harvests, holder rewards and donations can also be paid straight into it.
There is one pool for the whole site. Harvests, holder rewards and donation payouts of every coin, and every shield on Move BNB, add notes to the same tree, so each note hides among all of them, not only among notes from the same coin.
Field BN254 scalar field
Hash Poseidon
Note commitment = Poseidon(amount, pubKey, blinding)
Keypair pubKey = Poseidon(privKey); privKey = keccak(signature of "zkBNB shielded key v1") mod p
Nullifier Poseidon(commitment, leafIndex, Poseidon(privKey, commitment, leafIndex))
Tree depth 20, incremental, 100-root history
Join-split 2 inputs → 2 outputs, Groth16 on BN254, Powers of Tau 16
Address zkbnb1 + pubKey (32 bytes) + x25519 encryption key (32 bytes), hextransact(proof, extData) handles three cases: extAmount > 0 is a deposit (you send exactly that much BNB), extAmount < 0 is a withdrawal to recipient, and 0 is a private transfer. An optional fee is paid to relayer. Encrypted outputs are emitted with each new commitment, so a recipient finds their notes by trying to decrypt them. depositFor(pubKey, blinding) lets zkBNB contracts pay into the pool without a proof; the commitment is computed on-chain.
What is private
- Which note pays for which withdrawal or transfer (the spending graph inside the pool).
- The recipient of a private transfer, and the amount of each note created by a proof. Amounts are hidden by the commitment and range-checked inside the circuit, so nothing about them leaks on a private transfer.
- With the relayer, the wallet behind an unshield or a private transfer: the relayer submits the transaction, so its wallet is the only one on it.
- With a dark pool, the wallet behind a buy, a sell, a harvest or a shield-back of a coin: the trade is paid from your notes into a one-off vault and the proceeds come back as notes, so only the relayer's wallet is on those transactions (the way back still names your pubKey, see below).
What is not private
- Every shield: the sending wallet and the amount.
- Every unshield: the recipient address and the amount. Unshield to a fresh address. Unshielding to the wallet you shielded from links the two.
- Every contract payout into the pool (harvest, claim, donation settlement): the amount, the destination pubKey and the blinding are in the
DepositForevent. The harvester's or claimer's wallet signed that transaction. - Timing. A shield followed shortly by an unshield of the same amount is easy to match. Your privacy depends on how much activity the pool has.
- Whoever sends the
transacttransaction pays gas and ismsg.sender. Without the relayer that is your wallet; use the relayer on Move BNB or a wallet you do not mind linking. - Every dark-pool buy: the coin, the BNB amount (it is an unshield), the vault address and the tokens it received. Every sell, harvest or shield-back out of a vault: the vault, the amount and the pubKey it paid into, the same pubKey for all your vaults. Who stays hidden as long as no wallet has ever paid into that pubKey.
The relayer
An unshield or a private transfer can be handed to the site's relayer instead of being sent from your wallet. Your browser asks it for its address and fee, bakes both into the proof (extData.relayer, extData.fee), and posts the proof; the relayer submits transact from its own wallet and the pool pays it the fee out of your notes. Everything the transaction does is fixed by extDataHash, so the relayer cannot change the recipient, the amount or the fee: it can only decline to send. If no relayer is configured or it runs out of gas, the page falls back to your wallet and says so.
Standard sizes
Shields and unshields are public, including their amount. An amount nobody else uses links a shield to its unshield no matter how many notes sit in between. Move BNB offers 0.01, 0.02, 0.05, 0.1, 0.2, 0.5, 1, 2, 5 and 10 BNB and warns on other amounts; split a larger sum into those sizes over separate transactions, and unshield in the same sizes to a fresh address through the relayer. Inside the pool you can send any amount: private transfers do not reveal it.
Keys
Your shielded key is derived from a wallet signature and kept in memory only. Anyone who can sign with your wallet can derive your shielded key. Proofs are generated in your browser in a Web Worker; the proving key is about 15 to 20 MB and is downloaded once.
You can only lose shielded notes by losing the wallet you derived the key from. Notes are found again by scanning the pool's events; the copy cached in your browser is a convenience.
Limits
- Deposits through
transactare capped (100 BNB by default). Contract payouts throughdepositForare never capped, so they can never be blocked. - The withdrawal and relayer-fee limits are constants, so the admin cannot freeze withdrawals.
- The tree holds about a million notes. When it is full, the pool still pays out withdrawals: it can never lock funds.