New EIP Preps Ethereum Deposits for Quantum Threats

This material may contain third-party opinions, none of the data and information on this webpage constitutes investment advice according to our Disclaimer. While we adhere to strict Editorial Integrity, this post may contain references to products from our partners.

Ethereum developer kevaundray has submitted a draft proposal for a "post-quantum-ready deposit contract," aiming to add quantum-attack resistance to the contract that governs how validators stake and exit the network. PANews reported the proposal was submitted on GitHub, initially as EIP-12235 before being formally assigned the number EIP-8394, and remains in draft status pending editor review.

What the Proposal Changes

The draft would support variable-length validator deposits and introduce an irreversible BLS exit mode for the deposit contract — a design choice meant to close off a specific class of quantum-enabled attack rather than rework the entire contract. According to PANews, kevaundray noted in comments on the proposal that they are still waiting on feedback tied to three related EIPs — EIP-7251, EIP-8282 and EIP-7002 — before settling on a final design, underscoring that this is one piece of a broader, interdependent set of changes rather than a standalone fix.

Part of a Longer Quantum-Readiness Push

The proposal fits into Ethereum's wider, multi-year effort to prepare for quantum computing threats. Ethereum's own roadmap lays out a four-part overhaul spanning consensus signatures, data-availability commitments, account signatures and zero-knowledge proof systems, with core infrastructure work targeted for completion around 2029. The Ethereum Foundation has been explicit that no quantum computer today can actually break its cryptography, but flags that public keys already exposed on-chain make a "harvest now, decrypt later" attack a real long-term concern — exactly the kind of risk a hardened deposit contract is meant to close off, since validator deposits and exits touch some of the highest-value functions in the protocol.

What Happens From Here

As a draft still awaiting formal editor review, EIP-8394 is early in the standard EIP process and its design could change materially before any client teams commit to implementing it. The next concrete markers to watch are movement on the three EIPs kevaundray flagged as dependencies — 7251, 8282 and 7002 — since resolving those is what the proposal's own author says is needed before the deposit-contract design can be finalized.