The Ethereum privacy roadmap outlines three long-term priorities — private writes, private reads, and private proving — to embed privacy into core protocol layers while preserving scalability, with staged research and Layer 2 proofs targeted across 2025–2028.
Three pillars: private writes, private reads, private proving — each targets usability, data confidentiality, and proof efficiency.
Practical efforts include Layer 2 PlasmaFold, RPC privacy workgroups, and “prove anywhere” zero-knowledge tooling.
Roadmap driven by Ethereum Foundation’s Privacy Stewards of Ethereum (PSE) with community input from Vitalik Buterin and independent researchers.
Ethereum privacy roadmap: three pillars to embed privacy into protocol layers, see milestones and next steps — read the full update and timeline.
‘,
‘
🚀 Advanced Trading Tools Await You!
Maximize your potential. Join now and start trading!
‘,
‘
📈 Professional Trading Platform
Leverage advanced tools and a wide range of coins to boost your investments. Sign up now!
‘
];
var adplace = document.getElementById(“ads-bitget”);
if (adplace) {
var sessperindex = parseInt(sessionStorage.getItem(“adsindexBitget”));
var adsindex = isNaN(sessperindex) ? Math.floor(Math.random() * adscodesBitget.length) : sessperindex;
adplace.innerHTML = adscodesBitget[adsindex];
sessperindex = adsindex === adscodesBitget.length – 1 ? 0 : adsindex + 1;
sessionStorage.setItem(“adsindexBitget”, sessperindex);
}
})();
What is the Ethereum privacy roadmap?
Ethereum privacy roadmap is a publicly shared multi-year plan by the Privacy Stewards of Ethereum to make privacy a native property of the protocol. It prioritizes three pillars — private writes, private reads, and private proving — and balances confidentiality with scalability.
How will the roadmap implement private writes, private reads, and private proving?
The roadmap targets discrete, testable projects. Private writes focus on cheap, private onchain transfers via Layer 2s such as PlasmaFold. Private reads address RPC leaks through privacy-preserving alternatives and working groups. Private proving aims to make zero-knowledge proofs easier to generate on consumer devices under the “prove anywhere” initiative.
‘,
‘
🔒 Secure and Fast Transactions
Diversify your investments with a wide range of coins. Join now!
‘,
‘
💎 The Easiest Way to Invest in Crypto
Dont wait to get started. Click now and discover the advantages!
‘
];
var adplace = document.getElementById(“ads-binance”);
if (adplace) {
var sessperindex = parseInt(sessionStorage.getItem(“adsindexBinance”));
var adsindex = isNaN(sessperindex) ? Math.floor(Math.random() * adscodesBinance.length) : sessperindex;
adplace.innerHTML = adscodesBinance[adsindex];
sessperindex = adsindex === adscodesBinance.length – 1 ? 0 : adsindex + 1;
sessionStorage.setItem(“adsindexBinance”, sessperindex);
}
})();
PSE plans near-term proof-of-concept demos in 2025, with broader research outputs and tooling across 2026–2028. Timelines depend on peer review, community testing, and performance benchmarks. Key public milestones include Devconnect demos in November 2025 and a 2025 report on private voting.
Built-in privacy prevents the network from becoming a surveillance layer. As Ethereum grows into a global settlement layer, onchain confidentiality protects user identity and intent, maintains regulatory balance in confidential DeFi, and preserves permissionless innovation.
Private writes rely on Layer 2 aggregation and optimized ZK circuits to lower gas per private transfer, aiming to match the efficiency of public transfers while adding confidentiality.
Private reads are designed to preserve dApp UX by offering privacy-preserving query patterns and middleware so developer workflows remain intact while user data is protected.
‘
];
var adplace = document.getElementById(“ads-htx”);
if (adplace) {
var sessperindex = parseInt(sessionStorage.getItem(“adsindexHtx”));
var adsindex = isNaN(sessperindex) ? Math.floor(Math.random() * adscodesHtx.length) : sessperindex;
adplace.innerHTML = adscodesHtx[adsindex];
sessperindex = adsindex === adscodesHtx.length – 1 ? 0 : adsindex + 1;
sessionStorage.setItem(“adsindexHtx”, sessperindex);
}
})();