Ethereum proposes deposit overhaul to quantum-proof staking

Ethereum core developers propose changing the deposit contract to let validators upgrade withdrawal credentials to post-quantum or hybrid keys to protect staked ether from future quantum attacks.

Ethereum core developers and researchers have proposed overhauling the on-chain deposit contract so validators can upgrade their withdrawal credentials to quantum-resistant keys. The change aims to protect staked ether and future withdrawals from potential quantum attacks.

Under the proposal, validators would replace current BLS-based withdrawal credentials with new keys that use post-quantum algorithms or hybrid combinations of classical and post-quantum schemes. Validators would authorize a change by signing an authorization with their existing BLS validator key and submitting an on-chain transaction that updates the stored withdrawal credential.

The draft specifies a new deposit contract function that accepts the signed authorization and checks that signature using existing consensus rules before updating the on-chain withdrawal credential. The design includes support for hybrid keys, where a classical BLS component is paired with a post-quantum component so withdrawals require both parts.

The proposal notes that the cryptography behind BLS is vulnerable to quantum algorithms such as Shor’s algorithm. A sufficiently powerful quantum computer could, in theory, recover private keys and enable unauthorized withdrawals. The contract change creates a standardized, authenticated migration path to algorithms intended to resist such attacks.

Developers flagged trade-offs. Many post-quantum signature schemes produce larger public keys or signatures, which increase gas costs and on-chain storage. To limit costs, the proposal suggests committing a compact hash of a post-quantum public key on-chain and revealing or using the full key off-chain in some flows, or using hybrid designs and key-encapsulation mechanisms to reduce on-chain payloads. Any on-chain validation of large signatures would increase transaction costs for validators during the migration.

A change to the deposit contract would require a coordinated network upgrade and client-level support across execution and consensus clients. Developers plan to formalize the work through the Ethereum Improvement Proposal (EIP) process, test implementations in client software, and schedule a protocol upgrade. The proposal anticipates a phased rollout so validators, staking providers and custodial services can prepare tooling and procedures. Migration would be opt-in; validators who do not migrate would retain current credentials and withdrawal behavior.

The proposal has been discussed in Ethereum core developer meetings and research channels. Participants weighed which post-quantum algorithms to support, estimated gas costs and considered user experience for staking providers and individual validators. Developers referenced NIST’s post-quantum selection work and suggested hybrid schemes that pair selected PQC candidates with BLS for added redundancy.

Background: Ethereum moved to proof-of-stake in 2022. The deposit contract stores validator public keys and a 32-byte withdrawal credential that determines how validators claim withdrawn funds. Research and standardization of quantum-resistant cryptography are ongoing; protocol designers note that on-chain assets and withdrawal rights can remain sensitive for many years, so migration options are being prepared now.

The material on GNcrypto is intended solely for informational use and must not be regarded as financial advice. We make every effort to keep the content accurate and current, but we cannot warrant its precision, completeness, or reliability. GNcrypto does not take responsibility for any mistakes, omissions, or financial losses resulting from reliance on this information. Any actions you take based on this content are done at your own risk. Always conduct independent research and seek guidance from a qualified specialist. For further details, please review our Terms, Privacy Policy and Disclaimers.

Articles by this author