TechFlow Logo
Login/ Sign up
ETH Gas
Gwei
Fear
gas
Are Crypto Assets Still Secure in the Quantum Computing Era? A Look at Ethereum's Post-Quantum Roadmap

Are Crypto Assets Still Secure in the Quantum Computing Era? A Look at Ethereum's Post-Quantum Roadmap

2026.11.18
Share
Quantum computing has not yet posed a realistic threat, but it is already forcing blockchains to redesign account authorization, key management, and asset migration mechanisms.

Written by: imToken

If one day, a quantum computer could derive a private key from an exposed public key on-chain in a very short time, would the crypto asset security system built on cryptography today still hold?

For a long time, discussions on quantum computing in the crypto industry remained at the theoretical level: acknowledging that elliptic curve cryptography widely used by mainstream blockchains like Bitcoin and Ethereum could potentially be broken by quantum computers with sufficient computing power in the future, but it remains relatively distant.

In fact, by 2026, this issue has officially moved into the engineering implementation phase. The Ethereum Foundation not only established a dedicated post-quantum security research team, but also set a late-2029 deadline in its latest protocol roadmap as the engineering goal for L1 to fully achieve post-quantum resistance across the execution layer, consensus layer, and data layer.

For an open network with hundreds of millions of accounts, massive asset scale, and a complex application ecosystem, migrating the cryptographic system is far more than a simple software upgrade.

Especially from the perspective of ordinary users, the real challenge often lies not in "how to generate a new post-quantum private key," but in how to securely and seamlessly control existing accounts and assets while transitioning to a new signature algorithm.

What does quantum computing actually threaten?

To understand the impact of quantum computing on crypto assets, we first need to break down the blockchain security architecture.

Ethereum currently relies on four main cryptographic components to function, each serving accounts, consensus, data availability, and application-layer proofs. They solve different problems and have unequal risk exposures to quantum computing:

  • ECDSA: Elliptic Curve Digital Signature Algorithm used by ordinary user accounts to prove transaction initiator ownership;
  • BLS: Signature algorithm used in Ethereum's PoS consensus layer, capable of efficiently aggregating votes from hundreds of thousands of validators into a single signature;
  • ZK-proof systems: Zero-knowledge proof systems used by applications like Rollups;
  • KZG: Polynomial commitment scheme used for verifying Blob and Rollup data availability (DA);

Among them, ECDSA and BLS, asymmetric cryptography based on the elliptic curve discrete logarithm problem, are the first to bear the brunt.

As is well known, traditional computers cannot feasibly reverse-engineer a private key from a public key. However, fault-tolerant quantum computers running Shor's algorithm can theoretically solve the elliptic curve discrete logarithm problem in polynomial time, thereby breaking the public-key cryptographic security of ECDSA, BLS, and other systems relying on related mathematical assumptions.

Once a private key is restored, an attacker can directly forge valid signatures to transfer assets without stealing mnemonic phrases or compromising wallet clients. Similarly, validator keys, protocol multisig management permissions, and cross-chain bridge control keys all face similar long-term vulnerabilities.

In contrast, hash functions like Keccak-256 are more resilient to quantum computing. Although Grover's algorithm offers quadratic speedup, it does not directly reduce exponential-time security problems to polynomial-time solvable ones like Shor's algorithm does.

This leads to a commonly overlooked critical detail: not all Ethereum accounts face the same level of risk under quantum threats.

An ordinary Ethereum EOA address is derived by taking the public key, hashing it with Keccak-256, and truncating the result.

Therefore, if a cold wallet has never initiated any on-chain transactions and has never publicly signed anything off-chain, only the hashed address is recorded on-chain. The full public key has never been exposed and remains protected by the one-way property of hashing; however, as soon as that address initiates even a single transfer or contract authorization, attackers can reconstruct the full public key from the publicly available transaction signature, directly exposing it to the risk of future elliptic curve breakthroughs.

Of course, no quantum computer with cryptographic-breaking capabilities exists globally at this stage, so ordinary users need not panic-transfer their assets.

The Ethereum Foundation's post-quantum team has also emphasized multiple times that fault-tolerant quantum computers posing a real threat still need to overcome significant engineering hurdles in hardware scaling and quantum error correction. (Further reading: "What exactly does quantum computing threaten? A Crypto user guide to the post-quantum era".)

The problem is, cryptographic migration itself takes years. If we wait until the threat materializes to start preparing, it may already be too late.

What preparations is Ethereum making?

In 2026, the Ethereum Foundation established a dedicated Post-Quantum Security team responsible for coordinating post-quantum cryptography research and engineering implementation at the protocol level.

Different from simply searching for a new signature algorithm, Ethereum is attempting to advance the upgrade of its cryptographic system simultaneously across three fronts: the execution layer, consensus layer, and data layer.

Execution Layer: Freeing Accounts from Permanent Binding to a Single Private Key

For ordinary users, the most direct change comes from the execution layer.

The account authorization logic for traditional Ethereum EOAs is relatively rigid: users generate signatures via a secp256k1 private key, and the network verifies their validity through ECDSA.

While this design is sufficiently simple and thoroughly tested over time, it tightly binds an account's identity to a specific signing scheme. If ECDSA becomes insecure in the future, users would need to switch algorithms. But merely swapping to a new private key often means generating a completely new account address, requiring the re-migration of existing assets, contract interaction histories, and application relationships.

This is clearly not an ideal solution.

To break these shackles, Ethereum is accelerating the push for native account abstraction, most notably represented by EIP-8141 (Further reading: "Native Account Abstraction + Post-Quantum Threats: Why Isn't EIP-8141 Ethereum's Top Topic Yet?").

It attempts to decouple transaction verification, actual execution, and gas payment into distinct stages, allowing accounts to determine whether a transaction is valid through programmable logic. This helps accounts gradually shed fixed reliance on ECDSA private keys, enables native key rotation, and leaves room for introducing different signature verification algorithms in the future.

Meanwhile, Ethereum is also researching post-quantum signature verification precompiles, enabling smart contracts and account validation logic to natively verify new signature types more efficiently.

But this is just the first step. Since post-quantum signatures are typically much larger than traditional ECDSA/BLS signatures, Ethereum must also address the resulting data and computational overhead. For instance, EIP-8288 proposes using recursive STARK aggregation to compress verification results of numerous post-quantum signatures into tighter proofs, thereby reducing on-chain data and verification burdens.

Consensus Layer: Replacing Traditional BLS with Hash-Based Signatures

Beyond the execution layer, the consensus layer is critical to Ethereum's underlying PoS operational mechanics.

Current PoS consensus heavily relies on BLS signature aggregation. Directly replacing it with standard post-quantum signatures would significantly increase P2P network propagation, storage, and verification costs due to the massive signature sizes.

To address this, Ethereum's Lean Ethereum roadmap has introduced two noteworthy technical directions.

  • leanXMSS: A hash-based post-quantum signature scheme planned to replace the BLS signatures currently used by validators, eliminating elliptic curve dependencies at the root;
  • leanVM: A minimal zero-knowledge virtual machine designed specifically for efficient post-quantum signature aggregation, attempting to compress vast numbers of validator hash signatures into compact proofs using recursive STARKs and other post-quantum ZK proofs, safeguarding consensus performance while ensuring post-quantum security;

This also illustrates that there is no universal "one-size-fits-all" algorithm for post-quantum upgrades; validator consensus and ordinary user wallets require tailored cryptographic tools that best suit their respective needs.

Data Layer: KZG and ZK Proofs Also Require Quantum Considerations

Beyond account and validator signatures, the data layer faces equally long-term challenges.

Ethereum has heavily adopted the KZG polynomial commitment mechanism in recent years, particularly for Blob and Rollup data availability. Since KZG's security relies on mathematical assumptions related to elliptic curve pairings, it must also account for the impact of future quantum computing.

Additionally, at the application layer, certain ZK proofs used by systems like Rollups face similar issues. Particularly, some SNARKs relying on elliptic curve pairings may see their security assumptions undermined by Shor's algorithm. In contrast, STARKs built on hash functions do not depend on elliptic curve discrete logarithm assumptions, granting them stronger post-quantum security properties.

This means post-quantum migration is not solely an Ethereum L1 concern; it will gradually need to extend to L2s, Rollups, and various on-chain applications in the future.

Timeline-wise, in the protocol priorities announced by the Ethereum Foundation in September 2026, it was explicitly stated that efforts will be made to achieve post-quantum resistance across the execution, consensus, and data layers of Ethereum L1 before December 2029. Subsequent upgrade nodes will also gradually introduce post-quantum infrastructure such as public key registration, signature verification, consensus proofs, and data commitments.

This will be a long-term project involving the entire ecosystem.

How to Safely Guide Users Through Asset Migration?

While the previous sections discussed how Ethereum addresses underlying cryptographic challenges, what matters most to ordinary users is what our wallets should do when the current signing system requires an upgrade?

This process is far more complex than simply regenerating a private key.

The first hurdle to address is account identity.

For traditional EOAs, there is a direct mathematical relationship between the account address and the public key. If users directly adopt a new post-quantum key system, they typically must generate a new account identity before transferring existing assets over.

But this creates a cascade of problems. Beyond ETH and ERC-20 tokens, users may hold NFTs, deposits and positions in DeFi protocols, and assets across various L2 networks. Some applications also tie permissions, loyalty points, interaction history, and social graphs to user addresses.

If every cryptographic upgrade requires switching account addresses, users would have to manually reconfigure these assets and application relationships, resulting in extremely high migration costs.

This highlights the importance of account abstraction, which can decouple account identity from underlying signing keys as much as possible, allowing accounts to determine who controls assets through programmable validation logic.

Theoretically, this means users will eventually have the option to switch underlying signature algorithms while retaining their original account address, avoiding the need to migrate all assets to a new location.

This is one of the core capabilities EIP-8141 aims to provide.

Secondly, migrating between old and new keys. An ideal migration process should be user-initiated authorization for a new post-quantum key to take over the account while the existing cryptographic system is still secure.

For example, a wallet could first generate a new post-quantum key in a secure environment, then authorize updates to the account's validation rules using a valid signature from the existing account.

If the original ECDSA private key remains secure, this process can follow normal account upgrade procedures. However, if a quantum computer already possesses the capability to crack existing private keys, the situation changes drastically.

At that point, both attackers and legitimate users might be able to forge signatures for the original account, making it nearly impossible for the system to determine rightful ownership based solely on the old key.

This is precisely why proactive migration is so crucial.

Furthermore, there is another particularly tricky category of accounts: those inactive for years, with lost private keys, or whose owners are entirely unaware that upgrades are necessary. These accounts may still hold significant assets but cannot proactively complete migration.

Whether to allow such assets to remain in their original addresses or implement measures like freezing them in the future through protocol governance remains highly debated.

Finally, and perhaps most easily overlooked, secure migration itself must not become a new attack vector.

As the industry begins discussing quantum threats, attackers are likely to exploit user anxiety by creating fake pages purporting to offer "quantum-safe upgrades," "private key verification," or "asset migration," tricking users into inputting mnemonics or signing malicious authorizations.

Therefore, future wallets must not only provide migration tools but also ensure users can clearly identify upgrade sources, verify transaction contents, and confirm exactly which assets are controlled by new authorization logic.

In Conclusion

From today's perspective, quantum computing is nowhere near powerful enough to directly threaten mainstream blockchain cryptographic systems.

But this does not mean the industry can ignore it.

The post-quantum roadmap Ethereum is advancing actually demonstrates that future blockchain security should not rest on the assumption that any specific cryptographic algorithm is unbreakable, but rather on the entire system's ability to continuously upgrade and securely migrate.

For ordinary users, the role of wallets will consequently evolve.

In the past, a wallet's core function was helping users generate, store, and use private keys. In the future, it will also need to help users understand account risks, manage keys across different cryptographic systems, and safely execute account upgrades when necessary.

This is not merely a replacement of signature algorithms; it represents an evolutionary leap for wallets from private key management tools to long-term asset security infrastructure.

At least today, users do not need to hastily migrate assets due to quantum computing. But for wallet developers and the broader crypto industry, the window for genuine early preparation has already begun.