Ethereum developers have proposed a new method for accepting staking deposits—a system through which network participants lock their ETH to become validators and verify transactions. The primary goal of the change is to preemptively protect against quantum computers, which in the future could theoretically break modern cryptography. The proposal was published on August 23, 2026, by developers Kevaundray Wedderburn, Tom Wambsgans, and Thomas Coratger.
Why This is Necessary at All
Currently, the security of Bitcoin, Ethereum, and most other cryptocurrencies relies on elliptic curve cryptography. In simple terms: it's a mathematical mechanism that allows proving that a transaction was sent by the wallet owner without revealing their private key. No existing computer is capable of breaking this protection yet.
The problem is that quantum computers are fundamentally different from conventional ones and can solve certain mathematical problems thousands of times faster. If such a machine becomes sufficiently powerful, it could compute a private key from a public one—and forge someone else's signature.
How Close Is This?
Opinions on this matter vary. In March 2026, Google published research indicating that breaking the cryptography of Bitcoin and Ethereum would require less than 500,000 qubits—20 times fewer than previously assumed. In other words, the assessment of the real threat has moved significantly closer over the past year.
Meanwhile, MicroStrategy founder Michael Saylor believes there will be no real threat to Bitcoin for at least another ten years—according to him, there is a consensus among cybersecurity specialists on this. Analytical company Grayscale holds a similar view: in its assessment, for investors today, the quantum threat is more a matter of trust in the system than an immediate technical danger to Bitcoin at the moment.
Regardless, major blockchains are not waiting for the problem to become real. Post-quantum protection is already being tested by Solana and XRP Ledger, and the Ethereum Foundation itself presented its own roadmap for transitioning to new cryptography back in February 2026—a plan spanning several years.
What the New Proposal Changes
The new deposit contract makes the system more flexible: it can accept keys of different types and lengths—up to 8,192 bytes, not just the format currently used (48 bytes). Each deposit receives its own label—a scheme identifier indicating exactly which type of cryptography was used. Label "0" is reserved for the current key format—the one already used by all active validators. The other labels are currently free: they will be assigned to specific post-quantum algorithms once developers choose them.
The way deposit data enters the network also changes. Instead of the old method of storing contribution records, they will now be transmitted via a separate message channel between the two network layers—the one that executes transactions and the one that coordinates and confirms them. This is a technical restructuring "under the hood" that does not affect how an ordinary user makes a deposit.
A safety mechanism is also built-in—a three-stage switching mode. Initially, accepting new deposits is disabled. Then the network enables the current key format—it continues to work as before. And only at the third stage, via a separate future upgrade, the old format is permanently disabled—without the possibility of reverting back. This is intentional: the transition to new cryptography must be manageable and predictable, not a sudden, one-time switch.
The Bottom Line
For now, this is only a draft, and there is no specific implementation date. But the very fact of such a proposal's appearance shows: the industry is laying the groundwork for transitioning to post-quantum protection in advance, even before quantum computers become a real danger—just in case assessments like Google's from March continue to shift the threat timeline closer.
AI Opinion
From a machine data analysis perspective, the logic behind the new technical proposal is one that HashTelegraph has already examined using the example of Google's March research: Ethereum is structurally vulnerable to the so-called "resting state" attack. A public key for an account, once revealed in a transaction, remains visible on the blockchain forever—a malicious actor does not need to intercept anything in advance; it is enough to wait until a quantum computer becomes sufficiently powerful and compute the private key from the data already accumulated on the chain. This fundamentally differentiates Ethereum from Bitcoin, where the risk is limited to the narrow window of the transaction itself.
The new deposit contract does not directly address this threat—it only prepares the infrastructure for a change in the signature algorithm. Whether the format's flexibility will provide sufficient protection for the already-published keys of millions of existing accounts, or if a separate key rotation mechanism will be required, is a question that falls outside the scope of the proposal itself.
end-content
