Three researchers, Kevaundray Wedderburn, Tom Wambsgans, and Thomas Coratger, proposed an EIP draft on August 24, 2026, to completely 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, an initial step toward phasing out the fixed-length BLS format currently in use.
Scheme 0 and the Path Away from BLS
Currently, Ethereum’s consensus layer relies heavily on BLS cryptography. This new draft changes how the network reads data from entities wishing to become validators. Moving forward, each deposit process will be required to include a dedicated cryptographic scheme identifier. The legacy BLS system in use today will be labeled as Scheme 0. Slots for subsequent numbers are intentionally left open to accommodate future cryptographic algorithms.
This transition is designed to operate through a phased migration mechanism rather than an overnight overhaul. Despite the gradual rollout, researchers included a strict rule at the end of the roadmap: the system features a deprecation kill switch. Once the network decides it is ready to fully transition to a new algorithm, BLS functionality can be disabled forever. This deactivation is permanent and cannot be reversed.
Under the hood, the proposal also cleans up remnants of Ethereum’s legacy architecture. The legacy data-reading mechanism relying on Merkle-tree structures will be completely dismantled. In its place, the network will utilize an execution-layer request system based on the EIP-7685 standard.
More Than Just a New Contract
One point emphasized in the draft is that having a post-quantum-ready deposit contract does not automatically make today’s Ethereum network immune to quantum computing attacks. This contract is merely akin to a renovated front gate. The network still urgently requires separate, more complex upgrades to the consensus layer before quantum-resistant claims can truly be realized.
The structure of this upgrade is also intertwined with a series of other network improvements. This draft cannot be executed 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 consolidation.
What Remains Unanswered
The draft, which editors suggested assigning the registration number EIP-8394, is still in its very early stages. The document has not even appeared on the official EIP publication website yet.
For the developer community and node operators, this proposal is merely an initial blueprint. Before it can reach the mainnet, this code must pass a long gauntlet of tests: rounds of technical discussions, rigorous security analyses from auditors, and adoption by software client developers. Because the road ahead is still lengthy, no working group has set a target hard fork or committed to a mainnet launch 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.
