Ethereum’s Post-Quantum Plan Starts With a New Validator Gateway
Ethereum developers are considering a new validator deposit architecture designed to remove one of the obstacles to eventually replacing BLS signatures with post-quantum alternatives.
Summary:
- Ethereum developers have proposed a new post-quantum-ready validator deposit contract.
- The design supports variable-length public keys and multiple cryptographic schemes.
- Existing BLS deposits would remain compatible during a controlled migration period.
- An irreversible switch could eventually prevent validators from making new BLS deposits.
A draft proposal submitted to the Ethereum EIPs repository on Aug. 24 introduces flexible public keys, cryptographic scheme identifiers and a mechanism for permanently retiring new BLS deposits once the network is ready to migrate.
Why Ethereum’s Current Deposit Design Creates a Migration Problem
Ethereum validators currently rely on BLS cryptography, with validator deposits carrying fixed-size BLS public keys and signatures.
That works efficiently for today’s consensus system, but those assumptions become restrictive if ETH eventually adopts a signature scheme with different key or signature sizes.
The proposed contract changes that architecture before Ethereum has to select a permanent post-quantum replacement.
Rather than hardcoding another cryptographic system into the deposit process, the design introduces a scheme identifier. Scheme 0 is reserved for Ethereum’s existing BLS deposits, while future identifiers could represent different signature systems.
Public keys and credential metadata would also become variable-length fields.
That distinction matters because post-quantum signature schemes can have substantially different data requirements from BLS. A deposit format built around flexible fields would allow Ethereum to introduce another cryptographic scheme without replacing the entire deposit interface again.
The proposal is currently a draft pull request, not an approved Ethereum upgrade. Its authors are Kevaundray Wedderburn, Tom Wambsgans and Thomas Coratger, and the specification remains subject to technical review and revision.
New Contract Would Remove the Legacy Merkle-Tree Dependency
The proposal also changes how validator deposits travel from Ethereum’s execution layer to its consensus layer.
Ethereum’s original staking deposit architecture relied on a deposit contract maintaining a Merkle tree that consensus clients monitored when processing new validators. More recent protocol work has already started moving away from that model.
EIP-6110 brought validator deposits directly into execution-layer block processing, while EIP-7685 established a generalized mechanism for passing requests from the execution layer to the consensus layer. Ethereum lists EIP-7685 as a finalized Core EIP.
The proposed post-quantum contract builds on that newer architecture rather than recreating the legacy deposit tree.
Instead, deposit information would move through execution requests using the EIP-7685 framework. That makes the proposal part of a broader simplification of communication between Ethereum’s two protocol layers rather than a standalone cryptographic change.
How Ethereum Could Retire BLS Without Disrupting Existing Validators
The most consequential part of the design is its migration mechanism.
Developers are not proposing to suddenly invalidate BLS deposits. Instead, the contract introduces protocol-controlled states that would allow Ethereum to move through the transition in stages.
The process could work roughly as follows:
- Deploy the new contract with deposits disabled, allowing infrastructure to prepare before it becomes operational.
- Enable BLS deposits through the new architecture at a protocol-selected point while existing infrastructure continues operating.
- Introduce alternative signature schemes through additional scheme identifiers as Ethereum’s post-quantum work matures.
- Permanently disable new BLS deposits once the network commits to moving beyond BLS.
The final step would be irreversible under the proposed design. Once BLS deposits are disabled, the contract could not simply switch them back on.
During migration, execution clients would need to combine deposit requests originating from both the legacy and replacement contracts, allowing the two systems to coexist rather than requiring a single disruptive cutover.
READ MORE: BitMine Adds 32,447 ETH as Ethereum Gains 30% Weekly to $2,514
That is particularly relevant for Ethereum because its validator population cannot realistically migrate cryptographic infrastructure simultaneously.
Post-Quantum Preparation Is Moving Into Ethereum’s Core Architecture
The proposal does not choose Ethereum’s eventual post-quantum signature algorithm. Instead, it attempts to ensure that the staking architecture can accommodate one later.
That separates two engineering problems that otherwise risk becoming intertwined.
Ethereum can first make validator deposits cryptographically flexible, then evaluate post-quantum schemes on their security, verification cost, signature size and implementation requirements.
Other protocol work points in the same direction. Ethereum’s EIP repository now includes EIP-8310, a draft proposal for a post-quantum keystore for stateful keys. Ethereum’s forward-compatible consensus data structure work also explicitly discusses future post-quantum transitions and the possibility that such a migration could require changes to existing Merkle structures.
The practical benefit is optionality. Ethereum would not need to know today which post-quantum signature scheme will ultimately replace BLS in order to remove fixed BLS assumptions from parts of its validator infrastructure.
What the Proposal Still Has to Solve
The harder part of the proposal is not adding support for another signature scheme, but defining how Ethereum would manage a period in which several validator credential formats could exist at the same time.
Before the contract could become part of a network upgrade, developers would need to settle how deposits from the legacy and replacement contracts are ordered and processed, how staking infrastructure identifies different scheme IDs, and how existing validator tooling handles variable-length public keys and credentials.
The proposal also intersects with other changes to Ethereum’s staking architecture. Its authors have specifically flagged interactions with EIP-7251, EIP-8282 and EIP-7002 as areas requiring further design feedback. Those dependencies matter because deposit processing, validator balances and withdrawal mechanics cannot be modified independently without considering how consensus clients interpret the resulting validator state.
The irreversible BLS switch creates another decision point. Supporting a post-quantum scheme does not automatically mean Ethereum is ready to stop accepting BLS validators. Developers would first need confidence in the replacement cryptography, client implementations and operational tooling before permanently closing the existing deposit route.
That makes the proposal’s next meaningful milestone more specific than simply advancing through the EIP process: whether developers can define a workable coexistence period between BLS and future signature schemes without introducing ambiguity into validator deposits. Only after that architecture is settled does the mechanism for permanently disabling new BLS deposits become practically relevant.
The information presented in this article is intended for informational purposes only and should not be interpreted as financial, investment, or trading advice. Coinspress.com does not promote or advocate for any particular investment strategy, asset, or cryptocurrency project. Cryptocurrency markets are highly volatile and unpredictable – always perform your own research and seek guidance from a qualified financial professional before making any investment decisions.
Alexander Stefanov
Reporter at CoinsPress
Alex is Editor-in-Chief of Coinspress and co-founder of Millennial Media Group, with nearly a decade of experience covering financial markets - crypto first, then everything else. It started in 2016 with Bitcoin. Like most people at the time, he didn't fully understand it - so he kept digging. Blockchain, tokenomics, the projects, the cycles. That curiosity never stopped, and eventually pulled him into traditional markets too: equities, commodities, macro. Not because he left crypto behind, but because you can't properly understand one without the other. What drives him is straightforward: he wants to know why something is happening, not just that it's happening. Most market coverage stops at the headline - price up, price down, here's a chart. Alex finds that kind of reporting actively unhelpful. If you walk away from an article without understanding the mechanism behind the move, what did you actually learn? He holds a degree in Tourism from New Bulgarian University - not the most obvious path into financial markets, but markets have a way of pulling in people who are simply too curious to stay out. He has authored over 200 in-depth analyses and more than 10,000 articles across crypto and traditional finance. He still thinks every day in markets teaches him something new. That's probably why he hasn't stopped.
