The developers purchased and repurchased 2% of the tokens, all of which were sent to CZ—because we consider him, too, to be a part of what we are building. $bunker

1/ The NewL1 privacy layer is a beautiful spec. BUNKER is a shipped product. Same cryptographic core — but we're not proposing it on a devnet, we built the whole thing and it runs on BNB Smart Chain today. Here's the technical head-to-head. 🛡️ 2/ Same foundation, so let's be precise: note/nullifier accounting, Groth16 over BN254, a Poseidon commitment tree. cm = Poseidon(asset, value, address, rho, rcm), nf = Poseidon(nk, rho, pos). We don't dispute their design — we implemented it. 3/ Root window: they keep a 64-root ring, giving ~640s of proof-submission headroom. We run a 128-root ring — double the window, so a proof you generated stays valid far longer under congestion. More forgiving for real users on a busy chain. 4/ Accounting integrity: they track a totalShielded custody counter. We go further with a share-based pool per asset plus a hard turnstile invariant total_out ≤ total_in, and a virtual offset that kills first-depositor / inflation attacks outright. Over-withdrawal isn't "checked" — it's mathematically impossible. 5/ Composability: their killer feature is atomicCall — unshield → DeFi → reshield in one atomic tx. We built the same pattern as a production exit hook: unshield → one-time secp256k1 claim key → trade → re-shield. The chain only ever sees "the pool interacted," never who. 6/ And here's where we're simply ahead: their "privacy swap / privacy launchpad" is listed under section 4.5 — future scenarios. We already shipped the launchpad. Fully private token launches, private buys/sells, graduation to PancakeSwap V2 with LP burned. Live, not roadmap. 7/ Governance: no admin can touch pooled funds in either design. But our fee policy is run by 4 on-chain autonomous agents with deterministic epochs — the fee for epoch E is computable before E starts, so a relayer can never move your min_out under you. Trust-minimized by construction. 8/ Compliance: we agree with their "guard the entrance, never the exit" principle, and implemented it as voluntary ASP association-set roots — prove membership if you want, withdraw is never gateable. Privacy and optional compliance, no forced KYC. 9/ Where they'll win later: a native 0x77 tx type (no EOA exposure) and a 0x67 Poseidon precompile (cheaper gas) need L1 changes. We run on PoseidonT3 in pure Solidity today — and the day those primitives land, BUNKER maps straight onto them. We're the app-layer head start. 10/ Bottom line: they wrote the paper. We shipped the protocol. Privacy pool + privacy launchpad, running on BNB Smart Chain now. BUNKER — Shielded. Private. Yours. forum.bnbchain.org/c/bnbchai…