Three researchers, Kevaundray Wedderburn, Tom Wambsgans, and Thomas Coratger, proposed a draft EIP on August 24, 2026, to overhaul Ethereum’s validator deposit contract. The new system is no longer rigid; it is designed to accept public keys and signatures of variable lengths, marking a preliminary step toward moving away from the fixed format of the current BLS system.
Scheme 0 and the Exit Path from BLS
Currently, Ethereum’s consensus layer heavily relies on BLS cryptography. The new draft changes how the network reads data from entities seeking to become validators. Each deposit process will require a dedicated cryptographic scheme identifier. The legacy BLS system used today will be designated as Scheme 0, leaving subsequent numerical slots open to accommodate future cryptographic algorithms.
This transition is designed to function via a gradual migration mechanism rather than an abrupt overnight overhaul. Despite the phased approach, the researchers included a strict rule at the end of the roadmap: a deprecation feature. Once the network decides it is fully ready to transition to new algorithms, BLS functionality can be permanently disabled - an irreversible cutoff.
Under the hood, the proposal also cleans up Ethereum’s legacy architecture. The legacy data-reading mechanism relying on Merkle tree structures will be completely dismantled. In its place, the network will adopt an execution layer requests system built on the EIP-7685 standard.
More Than Just a New Contract
One point emphasized in the draft is that having a deposit contract labeled post-quantum-ready does not automatically protect Ethereum from quantum computer attacks today. The contract merely serves as a renovated front gate. The network still requires separate, more complex upgrades across the consensus layer before quantum-resistant claims can truly be realized.
The upgrade structure is also tightly coupled with a broader series of network improvements. The draft cannot be deployed in isolation, as it directly depends on three interconnected core upgrades: EIP-6110, which reorganizes the deposit process; EIP-7002, to facilitate withdrawal mechanisms; and EIP-7251, which governs validator balance consolidation.
What Remains Unresolved
The draft, which editors suggested registering under EIP-8394, remains in an early stage. The document has not yet appeared on the official EIP publication repository.
For developers and node operators, the proposal represents only an initial blueprint. Before reaching the mainnet, the code must navigate a lengthy journey: technical discussions, rigorous security audits, and client software integration. With significant milestones ahead, no working group has set a target hard fork or committed to a mainnet timeline.
Reported by crypto.news.
Read also: How Crypto Staking Works and Its Risks
Disclaimer: This article is for informational and educational purposes only, not financial advice. Cryptocurrency assets are highly volatile and carry significant risk. Always do your own research (DYOR) and never invest more than you can afford to lose.
