“Traditional bilateral OTC agreements, ..., are vital for institutional funding and risk transfer, but private execution breeds opacity, friction, and counterparty risk. Onchain bilateral agreements transform this model by recording contract terms, collateral, and lifecycle events on a shared ledger to enable real-time transparency and programmability.”
->Parties engaging in OTC transactions tend to prefer accepting privacy risks over opting for transparency, don't they?
The Trusted Setup Ceremony for pERC20 protocol is officially launching.
👉Only 1 click to join: ceremony.plabs.online
This is more than the birth of a protocol — it marks the beginning of privacy's story on the EVM. For the first time, the issuance, transfer, and burning of
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.
🖼 plabs4.github.io/awesome_ethpri…
📂 github.com/PLabs4/awesome…
———
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.
→ eips.ethereum.org/EIPS/eip-8182
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).
→ eips.ethereum.org/EIPS/eip-8250
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
→ eips.ethereum.org/EIPS/eip-8141
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).
→ github.com/ethereum/ERCs/…
→ ethsystems.org/approaches/app…
5) Kohaku (EF) — privacy wallet & SDK
Goal: make it easy for any wallet to integrate privacy.
→ GitHub: github.com/ethereum/kohaku
→ Roadmap: notes.ethereum.org/@niard/KohakuR…
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.
→ github.com/leanEthereum/l…
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: zips.z.cash/protocol/proto…
8) Compliance
• Privacy Pools / @0xbowio — deposit association sets at withdraw (ASP)
→ privacypools.com/whitepaper.pdf
• @RAILGUN_Project — Proof of Innocence at shield vs List Provider bad-lists
→ docs.railgun.org/wiki/assurance…
• @_PLabs — cmx association sets when spending
→ plabs.gitbook.io/plabs-docs/pri…
9) ETH & ERC-20 · DeFi Interaction
• ETH & ERC-20 shield — @RAILGUN_Project · @0xbowio.
• DeFi interaction — @RAILGUN_Project(unshield →contract call →shield );
→ docs.railgun.org/wiki/learn/int…
10) Offical Scope
• @VitalikButerin — simple L1 privacy roadmap
→ ethereum-magicians.org/t/a-maximally-…
• @VitalikButerin — the Ethereum long-term trajectory
→ strawmap.org
———
Corrections and new links welcome.
Interesting use case, @eth_systemsethsystems.org/approaches/app…
But only an on-chain dark pool (CLOB-based) can satisfy these requirements; no shield protocol could handle this case.
Today we're launching EthSystems.
We build confidential systems for institutional Ethereum.
Institutions want to use Ethereum, but one of the biggest problems is the lack of built-in, modular privacy tools.
We were the Ethereum Foundation's Institutional Privacy Task Force
2026: All rollups will be ZK
2027: All bridges will be ZK
Succinct has secured >$3B in bridge volume with @AcrossProtocol and @Agglayer.
... And we're just getting started.
782 Followers 4K Following|| Markets || $SPCX and Ether || Code || Fitness || Games || Lunarpunk || Fan of basketball, Zero Knowledge systems, and technology.
9K Followers 173 FollowingProfessor at Stanford University (https://t.co/LJLXu7aKyi, https://t.co/lwU5yWvC6W) Co-founder of Babylon protocol, Information theorist.
8.7M Followers 13 FollowingBitcoin is an open source censorship-resistant peer-to-peer immutable network. Trackable digital gold. Don't trust; verify. Not your keys; not your coins.
3K Followers 3K FollowingPartner @FactionVC. Advisor @LightspeedVP. Previously @DCGco. Fascinated by all things Crypto ∪ AI. Views are my own and posts never investment advice.
53K Followers 5K Following• 0 → 1 founder
• 500k+ users on products
• AI models running non-stop the last 120 days
• PhD in EdTech analytics/dashboards (h-index = 17)
16K Followers 915 FollowingBuilding the graduate school of blockchain engineering @rareskills_io
Passively open to new job opportunities?: https://t.co/xRu6uLmyrF
6K Followers 671 FollowingTweeting about, zero-knowledge, privacy, network design and MEV. President, Co-founder @aztecnetwork CEO @AztecLabs_
Views are my own.