Where BNB Veil goes from here 🟡
The foundation is in place, and it's running on BSC mainnet:
• A Privacy Pools–based ZK pool with ASP screening
• Bonding-curve launches with graduation to PancakeSwap V3
• An on-chain adapter that turns a proof into a private trade in one transaction
• A relayer so users never need a funded fresh wallet
• Private donations with optional receipts
• Creator rewards with an optional private claim
• Open-source contracts
That was the hard part: proving privacy, memes and public good can share one protocol.
The next part is making it effortless. Our focus now is packaging:
• More one-click flows. Private buy, private withdraw and private claim, each as simple as the new donation page
• Shareable links and embeds. A private-donation button any creator, community or charity can drop into their bio or website
• Builder tooling. Clean interfaces so other apps on BNB Chain can plug into the pool instead of rebuilding it
• Smoother onboarding. Fewer steps, clearer progress, easy to use on mobile
• A healthier pool. More everyday use means a bigger anonymity set, and better privacy for everyone in it
The protocol stays the same: non-custodial, screened deposits, proofs generated in your own browser. What changes is how easy it feels.
Privacy shouldn't need a manual. We'll keep shipping until it doesn't.
https://t.co/YYDyzoRrY2
https://t.co/GZWS1CgSvf
Private donations on BNB Chain just got one-click simple 🟡
Open a link, pick an amount, sign once, and confirm one deposit. Your browser handles the rest:
• Deposit enters the BNB Veil privacy pool
• Screened by the ASP, then mixed with other deposits
• A zero-knowledge proof is generated locally in your browser
• A decentralized relayer delivers the donation straight to the recipient
What’s public: the campaign’s address, total raised, and transaction amounts.
What’s not: which wallet gave.
• No seed phrase to write down: your keys are derived from a single wallet signature
• Close the page anytime: return with the same wallet and resume right where you left off
• Optional receipt: prove "this gift was mine" later—only if you choose to
• Changed your mind before it’s sent? Instant refund back to your original wallet
Built for creators, KOLs, and public goods that want support without asking supporters to expose their net worth or identity.
The first campaign is now live — the BNB Veil Community Fund:
👉 https://t.co/Bes2O7st4Y
Want a private donation link for your project or cause? Create a campaign on the Donate page and share it with your community. (0/1)
To everyone building, launching and showing up on BNB Chain: keep going 🟡
A few weeks ago, "privacy + memes + public good" sounded like a pitch deck idea.
Today it runs on BSC mainnet: real deposits, real proofs, real tokens, open-source contracts.
That didn't happen because of one team. It happened because people tried it early, asked hard questions, reported bugs, and kept coming back.
So here's an open invitation:
• Creators: launch your idea. The curve is fair, 70% of the curve fee goes to you, and you can claim it privately
• Traders: try one private buy. Deposit, wait a little, and see a ZK proof generated in your own browser
• Givers: open a campaign for something you care about, or support one without needing to explain yourself
• Builders: read the contracts, break things, tell us what's missing
You don't need to be an expert in zero-knowledge to use it. That's the point: privacy should feel as normal as sending a transaction.
Every launch, every deposit and every donation makes the pool stronger for the next person. Privacy is a team sport.
Small steps, done in public, add up. Let's build the next chapter of BNB Chain together.
Start here → https://t.co/YYDyzoRrY2
Code → https://t.co/GZWS1CgSvf
@nina_rong We've built exactly this, and it's already live on BNB Chain mainnet:
• Meme: bonding-curve launches with a 1% curve fee, 70% to the creator and 30% to buy back $BVeil, then graduation to PancakeSwap V3
• Privacy: a Privacy Pools–based ZK pool. Groth16 proofs are generated in the browser, deposits are ASP-screened, and an on-chain adapter turns a proof into a trade in one transaction
• Public good: anyone can open a donation campaign funded straight from the pool, with public totals and optional donor receipts
Open-source contracts: https://t.co/GZWS1CgSvf
Try it: https://t.co/YYDyzoRrY2
Would love to connect with the BNB Chain team 🙏
New on BNB Veil: withdraw BNB to a brand-new address, privately 🟡
Until now, BNB in the privacy pool could go out three ways: a private buy, a private donation, or a ragequit back to where it came from. Now there's a fourth: send it to any fresh address, with no link back to your deposit.
How it works:
1. Pick an approved note in your private vault
2. Choose a standard lot: 0.01 / 0.05 / 0.1 / 0.5 / 1 BNB
3. Enter a fresh address that has never interacted with your public wallet
4. Your browser generates a zero-knowledge proof locally
5. The relayer submits it and pays the gas. The fresh address receives the BNB minus a small relay fee
What the chain sees: the relayer paying some address a standard amount.
What it can't see: which deposit it came from.
Why only standard lots?
If you deposit 0.73 BNB and later withdraw exactly 0.73 BNB, the amount alone gives you away. Fixed lots make your withdrawal look like everyone else's. Leftover change stays in your note for next time.
Why the relayer?
A brand-new address has no BNB for gas. If you funded it from your main wallet first, you'd link the two yourself. The relayer pays the gas and takes its fee from the withdrawal, so the new address never needs to touch your old one.
Tips for the best privacy:
• Wait until a few more deposits land after yours (the vault shows the anonymity set)
• Use the random delay option
• Never send the withdrawn BNB straight back to your public wallet
Same rules as the rest of the pool: deposits are screened by the ASP, there's no custodian, and the keys stay in your vault.
Try it → https://t.co/YYDyzoRrY2
Private donations on BNB Veil: support KOLs and causes without exposing your wallet 🟡
How it works:
1. Anyone creates a campaign: recipient address + title. Funds go straight to the recipient in the same tx; the contract holds nothing.
2. Donors deposit BNB into the privacy pool first.
3. Donate "via privacy pool" in standard lots. Your browser generates a ZK proof and a relayer submits it. On-chain, the donor shows up as the donation contract, not your wallet.
4. Optional receipt: a secret only you hold. Present it anytime to prove "this donation was mine". Don't, and nobody can link it to you.
What stays public: campaign totals, donation count, timing. Every BNB is verifiable.
What stays private: which wallet donated.
Where this matters:
• Tipping KOLs and creators without your wallet being tracked, copy-traded or doxxed
• Charity and humanitarian causes where donors shouldn't have to publish their stance
• Disaster relief: the recipient is transparent, donors aren't exposed to scam targeting
• Open-source grants, bug bounties, community fundraising
• Matching or recognition later: show the receipt, not your whole wallet
Tip: always verify a campaign's address through the recipient's official channel, and give the pool some time before donating.
Donate privately → https://t.co/YYDyzoQU8u
Creator rewards are live on BNB Veil, with an optional private claim 🟡
Launch a token on https://t.co/YYDyzoRrY2 and earn from every trade on its bonding curve.
The 1% curve fee splits:
• 0.7% → the token creator
• 0.3% → buys back $BVeil
• After graduation to PancakeSwap: 0 fee
Two ways to receive:
1) Default: automatic payout to your creator wallet (or any address you set by signing a message). Paid every 4 hours once you're owed ≥ 0.01 BNB. No claim tx, no gas.
2) Private claim (optional): open your token page → connect the creator wallet → unlock your private vault → sign once.
Rewards are then deposited into the BNB Veil privacy pool in standard lots, and only your vault holds the secrets. When you want the BNB, use "Withdraw BNB to a new address": a ZK proof, submitted by the relayer, so the withdrawal can't be matched to the deposit on-chain.
Fully on the books:
• Every token page shows curve fees and creator earned / paid / pending, with tx links
• Docs → Buybacks & rewards shows the buyback ledger
• Buybacks wait until 0.1 BNB builds up, so gas and tax stay small
Tokens launched before today get back-pay automatically.
Launch → https://t.co/YYDyzoRrY2
CoinGecko listing request submitted.
Request ID: CL0510260015
GeckoTerminal: https://t.co/TgkEx6AcwA
Status: pending review. This is not confirmation of listing.
CoinGecko listing request submitted.
Request ID: CL0510260015
GeckoTerminal: https://t.co/TgkEx6AcwA
Status: pending review. This is not confirmation of listing.
BNB Veil is preparing a CoinGecko listing request for $BVeil on BNB Chain.
CA: 0x48619b0dd0680F2C9dCFDaaCdE80a3A732497777
GeckoTerminal: https://t.co/TgkEx6AcwA
Website: https://t.co/8YevC5tfb4
Application only—not confirmation of listing.
Creator rewards are coming to BNB Veil 🟡
Launch a token on BNB Veil and earn from every trade on its bonding curve:
• 0.7% of every curve trade goes to the creator
• 0.3% goes to buying back $BVeil
• 0% platform fee after graduation: once your token moves to PancakeSwap, we take nothing
Rewards are paid out every few hours, automatically.
And because this is a privacy platform, you can receive them privately:
choose any payout address, even a brand-new one, so your earnings never land in the wallet you launched from.
Every trade and every fee is on-chain in the Portal's events. Anyone can check that creators got their 70%.
Launch free. Earn on every trade. Get paid privately.
🌐 https://t.co/EUQx2SXjGp
📖 https://t.co/BmtU1MQKeU
Build in public: what shipped on BNB Veil this week 🛠
Protocol
• Creator locks are now optional. Lock your dev buy with a 30-day linear vest, or don't, and either way buyers see it on-chain and on every token page
• New Portal & adapter redeployed, verified on BscScan and Sourcify, and synced to our public repo the same day
Privacy infrastructure
• ASP sanctions screening and on-chain root publishing running live on mainnet
• Full-history log access, so recovering your vault from a 12-word phrase works no matter how long ago you deposited
• Relayer now quotes at the real network gas price, so private trades cost less
Launchpad
• Every token launched on BNB Veil is shown as verified source on BscScan automatically
• Token pages with USD market cap (via Chainlink), price, 24h volume, live K-line and social links
• "Latest tokens" feed on the homepage
Transparency
• Docs with every contract address, rule and fee in one place
• Open-source contracts: https://t.co/ZPU7E18H3r
Shipping daily. Privacy on BNB Chain is being built in the open, and you're early. 🟡
🌐 https://t.co/EUQx2SXjGp
$BVeil just printed a new all-time high. 📈
But the chart is the least interesting part. Look at what's underneath it:
🔐 A live zero-knowledge privacy pool on BNB Chain mainnet. Not a testnet, not a whitepaper.
🛡 Sanctions screening built into the protocol, the compliant design behind Privacy Pools (co-authored by Vitalik).
⚡️ Private buys, sells and donations in one transaction, through a relayer, to fresh one-time addresses.
🚀 A bonding-curve launchpad with privacy built in from day one.
🧩 Fully open source, every contract verified on BscScan.
🔑 Non-custodial: proofs and keys never leave the user's browser.
This isn't a meme with a roadmap. It's infrastructure that's already running.
Every chain eventually needs a privacy layer that regulators can live with. On Ethereum, that layer is being built by well-funded teams. On BNB Chain, it's live today, and it's early.
So here's the real question:
What is the first native, compliant privacy layer on BNB Chain worth? 🤔
The anonymity set is still small. Every deposit makes the privacy stronger for everyone after. That's what being early to infrastructure looks like.
🟡 $BVeil: 0x48619b0dd0680F2C9dCFDaaCdE80a3A732497777
🌐 https://t.co/EUQx2SXjGp
🔗 https://t.co/ZPU7E18H3r
Privacy 101 #3: Why doesn't your wallet send the transaction?
Because the sender is the loudest clue on-chain.
Say you withdraw from the privacy pool with a perfect zero-knowledge proof, but you submit it from your own wallet. Now the transaction shows your address paying the gas. Every bit of privacy the proof created, undone by one signature.
So on BNB Veil, a relayer submits it for you:
1. Your browser builds the zero-knowledge proof
2. It hands the proof to the relayer
3. The relayer sends the transaction and pays the gas
4. A small fee (0.3%) is taken from the withdrawn amount, never from your wallet
On-chain, you see the relayer, the pool and a fresh one-time address. Your main wallet is nowhere.
"Can the relayer steal or redirect my funds?"
No. The proof is bound to the exact recipient, amount and fee. If the relayer changes anything, the proof fails and the transaction reverts. The relayer can only deliver exactly what you signed off on, or nothing.
"What about timing?"
You can add an optional ~10-minute delay, so your withdrawal doesn't land right after you click.
The relayer is a courier that can't open the envelope.
Open source, verified on BscScan:
🔗 https://t.co/ZPU7E18H3r
Next up: what the ASP does, and why BNB Veil is not a mixer.
🌐 https://t.co/EUQx2SXjGp
Privacy 101 #2: Why does BNB Veil only take standard amounts like 0.1 or 1 BNB?
Because amounts are fingerprints.
Imagine you deposit 0.3721 BNB, and an hour later someone withdraws 0.3721 BNB. Zero-knowledge proofs hide WHICH deposit was spent, but an odd amount gives it away anyway. Anyone can just match the numbers.
So BNB Veil works in standard lots:
1 · 0.5 · 0.1 · 0.05 · 0.01 BNB
When everyone moves money in the same sizes, every 0.1 BNB withdrawal looks like every other 0.1 BNB deposit. You hide in the crowd instead of standing out.
It goes further than deposits:
• When you buy privately, the change left after the trade is split back into standard lots and re-deposited
• When you sell privately, the proceeds go back into the pool as standard lots too
• Anything smaller than 0.01 BNB is paid straight back, so no odd remainder sits in the pool pointing at you
Same idea as cash: a $20 bill tells you nothing about who held it before. A check for $37.41 does.
The bigger the crowd in each lot size, the stronger everyone's privacy. That's why early deposits matter.
Open source, verified on BscScan:
🔗 https://t.co/ZPU7E18H3r
Next up: why a relayer submits your transaction, not your wallet.
🌐 https://t.co/EUQx2SXjGp
Privacy 101 #1: How can a pool pay you without knowing which deposit is yours? 🧵
The trick is a "nullifier".
When you deposit, your browser makes two random numbers: a nullifier and a secret. Only their hash goes on-chain, so nobody can tell which deposit is yours.
When you withdraw, you show two things:
• a zero-knowledge proof that you know the secret behind SOME deposit in the pool
• the hash of your nullifier
The proof says "I own one of these deposits" without saying which one.
The nullifier hash is like a ticket stub: the contract records it, so the same deposit can never be spent twice.
So the pool can be sure that:
✅ you really own a deposit
✅ you haven't withdrawn it before
❌ but it has no idea which deposit it was
That's the core of BNB Veil's privacy pool, running on BNB Chain today.
Next: why we only accept standard amounts like 0.1 or 1 BNB.
🌐 https://t.co/EUQx2SXjGp