{"id":12444,"date":"2026-08-27T07:00:14","date_gmt":"2026-08-27T07:00:14","guid":{"rendered":"https:\/\/cryptonews.uk.com\/?p=12444"},"modified":"2026-08-27T07:00:14","modified_gmt":"2026-08-27T07:00:14","slug":"staking-ethereum-could-soon-look-entirely-different-under-a-new-deposit-proposal","status":"publish","type":"post","link":"https:\/\/cryptonews.uk.com\/?p=12444","title":{"rendered":"Staking Ethereum could soon look entirely different under a new deposit proposal"},"content":{"rendered":"

<\/p>\n

\n

Ethereum developers have opened an early proposal to make the staking deposit system flexible enough to accept future quantum-resistant validator keys, and it would also give a later network upgrade a one-way switch to stop new deposits using today\u2019s BLS format.<\/p>\n

The change would affect how new validators enter Ethereum, creating an entry path for future credential formats. Yet, those formats and the rules for verifying them still have to be designed and adopted separately.<\/p>\n

Pull request #12235 was opened Aug. 24 and remained an unmerged Draft as of Aug. 26, with its working file still using the placeholder number 9999. An Ethereum EIPs editor suggested assigning 8394, but the proposal has not been published or accepted as EIP-8394.<\/p>\n

How the deposit switch would work<\/h2>\n

Ethereum\u2019s staking deposit contract is the entry point that receives a prospective validator\u2019s funds and credential data. The current path expects public keys and signatures in fixed BLS12-381 formats.<\/p>\n

The draft specification instead adds a scheme identifier and variable-length fields for the public key and credential metadata, each capped at 8,192 bytes.<\/p>\n

Ethereum\u2019s execution layer can record a deposit while its consensus layer decides whether the credential is valid and can create or update a validator. Under the proposal, the contract would carry non-BLS credentials as opaque data, meaning it would transport the bytes without checking the new cryptography.<\/p>\n

\n

Related Reading<\/span><\/p>\n

Ethereum\u2019s massive fee shock: New post-quantum signatures are 40x larger, threatening to crush network throughput and user costs<\/h3>\n<\/p>\n

<\/span> <\/div>\n

The draft defines three contract modes: disabled, BLS enabled, and BLS retired. Those transitions only move forward, and once a protocol-controlled system call activates the retired mode, the new contract would reject BLS deposits and could not later switch BLS onboarding back on.<\/p>\n