What if, one day, a quantum computer could derive a private key from an exposed onchain public key in a matter of moments? Would today’s cryptography-based system for securing crypto assets still hold?
For years, the crypto industry treated quantum computing largely as a theoretical concern. Bitcoin, Ethereum, and other major blockchains rely heavily on elliptic-curve cryptography, which a sufficiently powerful quantum computer could eventually break—but the threat appeared distant.
By 2026, however, the issue had entered the engineering phase.
The Ethereum Foundation has established a dedicated post-quantum security team and set an engineering target for Ethereum L1 to achieve post-quantum resistance across the execution, consensus, and data layers by the end of 2029.
For an open network with hundreds of millions of accounts, vast amounts of capital, and a complex application ecosystem, replacing the underlying cryptography is far more involved than a routine software upgrade.
From an ordinary user’s perspective, the real challenge is not simply how to generate a new quantum-resistant private key. It is how to retain safe, uninterrupted control of existing accounts and assets while the signature system underneath them changes.
1. What Does Quantum Computing Actually Threaten?
To understand how quantum computing could affect crypto assets, we first need to examine the different cryptographic components that secure a blockchain.
Ethereum currently relies on four main categories of cryptography across its account, consensus, data availability, and application layers. Each serves a different purpose and faces a different level of quantum risk:
- ECDSA: The elliptic-curve digital signature algorithm used by standard user accounts to authorize transactions by proving control of the corresponding private key.
- BLS: The signature scheme used by Ethereum’s proof-of-stake consensus layer to aggregate votes from hundreds of thousands of validators efficiently.
- ZK proof systems: Zero-knowledge proof systems used by rollups and other applications.
- KZG: A polynomial commitment scheme used for blobs and rollup data availability.
The most immediate concern is asymmetric cryptography such as ECDSA and BLS, both of which rely on the difficulty of elliptic-curve discrete logarithm problems.
For a conventional computer, deriving a private key from a public key is considered computationally infeasible. A fault-tolerant quantum computer running Shor’s algorithm, however, could theoretically solve elliptic-curve discrete logarithm problems in polynomial time, undermining the security assumptions behind ECDSA, BLS, and related public-key cryptography.
If an attacker could recover a private key, they would not need to steal a seed phrase or compromise a wallet application. They could simply forge a valid signature and transfer the assets.
Validator keys, protocol-admin multisigs, and keys controlling cross-chain bridges would face similar long-term risks.
Hash functions such as Keccak-256 are more resilient to quantum computing. Grover’s algorithm can provide a quadratic speedup when searching for a preimage, but it does not reduce the problem from exponential difficulty to polynomial-time solvability in the way Shor’s algorithm does for elliptic-curve cryptography.
This leads to an important but often overlooked detail: not all Ethereum accounts face the same level of exposure to a future quantum attack.
An ordinary Ethereum externally owned account (EOA) address is derived by hashing the public key with Keccak-256 and taking the final 20 bytes.
If a cold wallet has never sent an onchain transaction and has never exposed a signature elsewhere, only its hashed address is visible onchain. The full public key remains hidden behind the one-way properties of the hash function.
Once that address sends even a single transfer or contract-approval transaction, however, its complete public key can be recovered from the public transaction signature. The key is then directly exposed to any future attack capable of breaking elliptic-curve cryptography.
No quantum computer capable of breaking mainstream cryptography exists today, so ordinary users do not need to move their assets in a panic.
The Ethereum Foundation’s post-quantum team has repeatedly emphasized that a cryptographically relevant fault-tolerant quantum computer would still require major advances in hardware scale and quantum error correction. Further reading: “What Does Quantum Computing Mean for Crypto Security?”
The problem is that cryptographic migrations take years. Waiting until the threat becomes real could leave too little time to respond.
2. How Is Ethereum Preparing?
In 2026, the Ethereum Foundation established a dedicated Post-Quantum Security team to coordinate protocol-level research and engineering for post-quantum cryptography.
Rather than simply searching for a replacement signature algorithm, Ethereum is working to upgrade its cryptographic foundations across the execution, consensus, and data layers simultaneously.
1. Execution Layer: Breaking the Permanent Link Between an Account and One Private Key
For ordinary users, the most direct changes will occur at the execution layer.
Traditional Ethereum EOAs use a relatively fixed authorization model: the user signs with a secp256k1 private key, and the network uses ECDSA to verify the signature.
This design is simple and battle-tested, but it tightly binds an account’s identity to one signature system.
If ECDSA becomes insecure, users will need to adopt a new signature algorithm. Simply generating a new private key, however, usually means creating a new account address. Existing assets, contract relationships, permissions, and application history may then need to be migrated as well.
That is far from ideal.
To loosen this dependency, Ethereum is accelerating work on native account abstraction, with EIP-8141 among the most prominent proposals.
Further reading: “Native Account Abstraction + the Quantum Threat: Why Was EIP-8141 Passed Over as the Headline Feature of Ethereum’s Hegotá Upgrade?”
EIP-8141 proposes separating transaction validation, execution, and gas payment into different frames. This would allow programmable logic to determine whether a transaction is valid, helping accounts move beyond permanent dependence on an ECDSA key.
It could also support native key rotation and create a path for accounts to adopt different signature-verification schemes in the future.
Ethereum is also researching precompiles for post-quantum signature verification, which would allow smart contracts and account-validation logic to verify new signature types more efficiently at the protocol level.
But this is only the first step.
Post-quantum signatures are generally much larger than conventional ECDSA or BLS signatures, so Ethereum must also address the resulting data and computational costs.
EIP-8288, for example, proposes using recursive STARK aggregation to compress the verification results of large numbers of post-quantum signatures into more compact proofs, reducing their onchain data and verification overhead.
2. Consensus Layer: Replacing BLS with Hash-Based Signatures
The consensus layer presents an even more fundamental challenge because it underpins Ethereum’s proof-of-stake mechanism.
Ethereum’s current consensus system relies heavily on the aggregation properties of BLS signatures. Replacing BLS directly with conventional post-quantum signatures would introduce much larger signatures, significantly increasing peer-to-peer propagation, storage, and verification costs.
Ethereum’s Lean Ethereum roadmap therefore explores two closely related technologies:
- leanXMSS: A hash-based post-quantum signature scheme intended to replace the BLS signatures currently used by validators, removing the validator signature scheme's dependence on elliptic curves.
- leanVM: A minimal proof-oriented virtual machine designed to aggregate post-quantum signatures efficiently. Through recursive proofs, it aims to compress large numbers of validator signatures into a compact proof, preserving consensus performance while providing quantum resistance.
This illustrates why there is no single universal algorithm for a post-quantum upgrade. Validator consensus and ordinary user wallets have different requirements and therefore need different cryptographic tools.
3. Data Layer: KZG and ZK Proofs Also Face Quantum-Security Challenges
The data layer faces long-term challenges of its own.
Ethereum increasingly relies on KZG polynomial commitments, particularly for blobs and rollup data availability. KZG depends on mathematical assumptions involving elliptic-curve pairings, so its long-term security must also be reassessed in the context of quantum computing.
Some ZK proof systems used by rollups and other applications face similar concerns. In particular, SNARK constructions that rely on elliptic-curve pairings may also be affected by Shor’s algorithm.
STARKs, by contrast, are built around hash functions and do not rely on the elliptic-curve discrete logarithm assumption, giving them stronger post-quantum security properties.
Post-quantum migration is therefore not solely an Ethereum L1 problem. It will eventually need to extend across L2s, rollups, and a wide range of onchain applications.
In its September 2026 protocol priorities update, the Ethereum Foundation set a target of December 2029 for Ethereum L1 to achieve post-quantum resistance across the execution, consensus, and data layers.
Future upgrades are expected to introduce the necessary infrastructure gradually, including post-quantum public-key registration, signature verification, consensus proofs, and quantum-resistant data commitments.
This will be a long-term effort involving the entire ecosystem.
3. How Can Users Migrate Their Assets Safely?
The first two sections concern Ethereum’s underlying cryptographic infrastructure. For ordinary users, however, the most important question is more practical: when existing signature systems need to be upgraded, what should wallets do?
The answer is far more complicated than generating a new private key.
The first challenge is account identity.
For a traditional EOA, the account address is mathematically linked to its public key. Moving to a new post-quantum key system would therefore typically mean creating a new account identity and transferring existing assets to it.
That creates a long list of complications.
Users may hold not only ETH and ERC-20 tokens, but also NFTs, deposits and positions in DeFi protocols, and assets across multiple L2 networks. Applications may associate the existing address with permissions, reward points, transaction history, or identity relationships.
If every cryptographic upgrade requires users to change addresses, all of these assets and application relationships may need to be handled again, making migration extremely costly and complex.
This is where account abstraction becomes especially important.
Account abstraction can separate an account’s identity from its underlying signing key as much as possible, allowing programmable validation logic to determine who has authority over the assets.
In theory, this could allow users to replace the underlying signature scheme while retaining the same account address, rather than moving every asset to a completely new address.
Creating this flexibility is one of the goals behind EIP-8141.
The second challenge is migrating from old keys to new ones.
An ideal migration would take place while the existing cryptographic system is still secure, allowing the user to authorize a new post-quantum key to take control of the account.
A wallet could generate a new post-quantum key in a secure environment and then use a valid signature from the existing account to update its validation rules.
As long as the original ECDSA private key remains secure, this can proceed like a normal account upgrade.
The situation changes entirely once a quantum computer can derive the existing private key from its public key.
At that point, both the genuine user and an attacker may be capable of producing signatures that appear valid under the old system. The network would have no reliable way to determine ownership based solely on the compromised key.
This is why migrating before the threat becomes practical is so important.
Another difficult category involves dormant accounts whose owners have lost their private keys, have not used the accounts for years, or are unaware that a migration is necessary.
These accounts may still hold significant assets, but their owners may be unable to initiate migration or may not realize that they need to do so.
Whether those assets should remain indefinitely at their existing addresses or eventually become subject to protocol-level measures such as freezing remains an open and controversial governance question.
Finally, the migration process itself must not become a new attack vector.
As the industry discusses quantum threats more frequently, attackers may exploit users’ fear by creating fake “quantum-security upgrades,” “private-key verification” tools, or “asset migration” websites designed to steal seed phrases or trick users into granting malicious approvals.
Wallets will therefore need to do more than provide migration tools. They must also help users verify where an upgrade request came from, understand exactly what a transaction will do, and confirm which assets the new authorization logic will control.
Final Thoughts
Quantum computers are still far from being able to threaten the cryptography used by mainstream blockchains directly.
But that does not mean the industry can ignore the risk.
Ethereum’s post-quantum roadmap reflects a broader principle: blockchain security should not depend on the assumption that one cryptographic algorithm will remain unbreakable forever. It should depend on the system’s ability to upgrade continuously and migrate safely when its assumptions change.
The role of wallets will evolve accordingly.
Until now, their primary responsibility has been to help users generate, store, and use private keys. In the future, wallets will also need to explain account-level risks, manage keys across different cryptographic systems, and help users upgrade their accounts safely when necessary.
This is more than a change in signature algorithms. It marks an evolution from wallets as private-key management tools into long-term infrastructure for asset security.
Users do not need to rush to move their assets because of quantum computing today. But for wallet developers and the broader crypto industry, now is the time to prepare.