We compiled @ethereum privacy discussions and designs into one living map — so anyone can see the privacy blueprint clearly: what’s being designed, why it matters, and who is behind it. Not an official roadmap. Continuously updated. 🖼 📂 ——— Core design 1) EIP-8182 — shared private UTXO pool Problem: app-level pools split liquidity — private funds stay fragmented. Vision: one protocol-owned shared pool that wallets and apps deposit into and spend from together. How: shared note-commitment tree + nullifier set. → 2) EIP-8250 — Keyed Nonce Problem: privacy flows often share one public sender / sponsor; a single linear nonce bottlenecks throughput — one inclusion can stall every other pending private spend. Vision: concurrent, independent private spends without a shared-sender queue. How: (nonce_keys, nonce_seq); non-overlapping keys are replay-independent (e.g. nullifier-derived keys). → 3) EIP-8141 — Frame Transactions Problem: bad UX for EOA users Vision: support arbitrary user-defined definitions of validation and gas payment. How: ordered frames — verify frame · approve frame · execution frame. Example: verify client proof + one time signature · approve trustless gas payemnt + execute call to privacy pool contract → 4) ERC-8302 — pERC20 (private fungible tokens) Requirments: bank wants to launch a private-stablecoin, informed by @eth_systems's research. Vision: stablecoins, RWA, or other assets may need privacy from day one. How: a private fungible token standard with an ERC-20-shaped surface (transfer / approve / allowance / transferFrom). → → 5) Kohaku (EF) — privacy wallet & SDK Goal: make it easy for any wallet to integrate privacy. → GitHub: → Roadmap: 6) leanVM — post-quantum proving & signatures Problem: ECDSA, BLS, and pairing SNARKs eventually break. Vision: hash-based signatures + PQ proof systems. How: leanXMSS + signature aggregation + recursive STARKs. → 7) Privacy Core Vision: value and addresses stay shielded in private transactions. How: UTXO notes + client ZKPs; IVK scanning + one-time receive addresses. → @zcash Protocol Spec: 8) Compliance • Privacy Pools / @0xbowio — deposit association sets at withdraw (ASP) → • @RAILGUN_Project — Proof of Innocence at shield vs List Provider bad-lists → • @_PLabs — cmx association sets when spending → 9) ETH & ERC-20 · DeFi Interaction • ETH & ERC-20 shield — @RAILGUN_Project · @0xbowio. • DeFi interaction — @RAILGUN_Project(unshield →contract call →shield ); → 10) Offical Scope • @VitalikButerin — simple L1 privacy roadmap → • @VitalikButerin — the Ethereum long-term trajectory → ——— Corrections and new links welcome.