Назад

In the Age of Quantum Computing, Are Crypto Assets Still Secure? Starting with Ethereum’s Post-Quantum Roadmap

НеутраленСподели вX (Twitter)Telegram

Quantum computing is not yet a real-world threat, but it is forcing blockchains to redesign account authorization, key management, and asset migration mechanisms.

Author: imToken

Quantum computing has not yet posed a real-world threat, but it is forcing blockchains to redesign account authorization, key management, and asset migration mechanisms.

Written by: imToken

If one day a quantum computer could derive private keys from public keys already exposed on-chain within a very short period, would the cryptography-based security framework for crypto assets that exists today still be considered valid?

For a long time, discussions around quantum computing in the crypto industry have largely remained at the theoretical level. It is acknowledged that elliptic curve cryptography widely used by mainstream blockchains like Bitcoin and Ethereum could eventually be compromised by quantum computers with sufficient computational power, but that scenario remains relatively distant.

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

For an open network with hundreds of millions of accounts, massive asset holdings, and a complex application ecosystem, replacing its cryptographic system is far from a simple software update.

Especially from the perspective of everyday users, the real challenge often does not lie in «how to generate a new post-quantum private key», but in how to securely and seamlessly retain control over existing accounts and assets while transitioning to new signature algorithms.

I. What Does Quantum Computing Actually Threaten?

To understand the impact of quantum computing on crypto assets, we must first deconstruct the blockchain security framework.

Currently, Ethereum relies primarily on four types of cryptographic components to operate, each serving accounts, consensus, data availability, and application-layer proofs. They solve different problems and face unequal risk exposures to quantum computing:

  • ECDSA: The elliptic curve digital signature algorithm used by ordinary user accounts to prove ownership of the transaction initiator;
  • BLS: The signature algorithm used in Ethereum's PoS consensus layer, which efficiently aggregates votes from hundreds of thousands of validators into a single signature;
  • ZK-proof systems: Zero-knowledge proof systems used by applications such as Rollups;
  • KZG: Polynomial commitment schemes used for validating Blob and Rollup data availability (DA);

Among these, asymmetric cryptography based on the elliptic curve discrete logarithm problem, such as ECDSA and BLS, faces the most immediate threat.

As is well known, deriving a private key from a public key is computationally infeasible for classical computers. However, fault-tolerant quantum computers running Shor's algorithm can theoretically solve the elliptic curve discrete logarithm problem in polynomial time, thereby undermining the security of public-key cryptosystems like ECDSA and BLS that rely on related mathematical assumptions.

Once private keys are recovered, attackers do not need to steal seed phrases or breach wallet clients; they can directly forge legitimate signatures to transfer assets. Similarly, validator keys, protocol multisig admin permissions, and cross-chain bridge control keys all face comparable long-term risks.

In contrast, hash functions represented by Keccak-256 are more resilient to quantum computing. While Grover's algorithm offers a quadratic speedup, it does not transform exponential-time security problems into polynomial-time solvable ones, unlike Shor's algorithm.

This brings up a frequently overlooked detail: not all Ethereum accounts face equal risk levels under quantum threats.

A standard Ethereum EOA address is derived by truncating the Keccak-256 hash of the public key.

Therefore, if your hardware wallet has never initiated any on-chain transactions, nor has any signature been publicly shared off-chain, then only the hashed address is recorded on-chain. The complete public key has never been exposed and remains protected by the one-way nature of hashing; however, once that address initiates even a single transfer or contract interaction, attackers can recover the full public key from the openly available transaction signatures, directly exposing it to the risk of future elliptic curve compromises.

Naturally, no quantum computer capable of cryptographic breaking has emerged globally as of yet, so everyday users need not panic-transfer their assets.

The Ethereum Foundation's post-quantum team has also repeatedly emphasized that fault-tolerant quantum computers posing actual threats still face significant engineering hurdles regarding hardware scale and quantum error correction (For further reading: What Exactly Does Quantum Computing Threaten? A Crypto User’s Guide to the Post-Quantum Era).

The critical issue, however, is that cryptographic migration itself requires years of preparation. If we wait until the threat actually materializes before starting, it may already be too late.

II. What Preparations Is Ethereum Making?

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

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

1. Execution Layer: Decoupling Accounts From Single Private Keys

For everyday users, the most direct changes stem from the execution layer.

The traditional account authorization logic for Ethereum EOAs is relatively rigid: users generate signatures using secp256k1 private keys, and the network verifies them via ECDSA.

While this design is sufficiently simple and has stood the test of time, it tightly couples an account's identity to a specific signature scheme. If ECDSA becomes insecure in the future, users will need to switch signature algorithms. However, simply obtaining a new private key usually means generating a new account address, potentially requiring the tedious migration of existing assets, smart contract interaction histories, and application relationships.

Certainly, this is not an ideal solution.

To break these shackles, Ethereum is accelerating the rollout of native account abstraction, most notably through EIP-8141 (For further reading: Native Account Abstraction + Anti-Quantum Threats: Why Isn’t EIP-8141 Ethereum’s Top Priority?).

It attempts to separate transaction validation, execution, and gas payment into distinct phases, allowing accounts to use programmable logic to determine whether a transaction is valid. This helps accounts gradually shed their rigid dependency on ECDSA private keys, enables native key rotation, and leaves room for integrating 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 merely 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 costs. For instance, EIP-8288 proposes utilizing recursive STARK aggregation to compress verification results from numerous post-quantum signatures into more compact proofs, thereby reducing on-chain data volume and verification overhead.

2. Consensus Layer: Replacing Traditional BLS With Hash-Based Signatures

Beyond the execution layer, the consensus layer is fundamental to Ethereum's underlying PoS operational mechanism.

Current PoS consensus heavily relies on the aggregation characteristics of BLS signatures. Directly replacing them with standard post-quantum signatures would significantly increase peer-to-peer (P2P) network propagation, storage, and verification costs due to the substantially larger signature sizes.

To address this, Ethereum's Lean Ethereum proposal outlines 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 source;
  • leanVM: An ultra-lightweight zero-knowledge virtual machine designed for the efficient aggregation of post-quantum signatures. It aims to compress hashes from numerous validators into compact proofs using recursive STARKs and other quantum-resistant ZKPs, maintaining baseline consensus performance while ensuring post-quantum security;

This illustrates that post-quantum upgrades lack a universal "silver bullet" algorithm. Validator consensus mechanisms and ordinary user wallets must each adopt the cryptographic tools that best fit their specific use cases.

3. Data Layer: KZG and ZK Proofs Also Require Quantum Security Considerations

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

Ethereum has extensively 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, its vulnerability to future quantum computing must also be addressed.

Additionally, at the application layer, certain ZK proofs used by systems like Rollups face similar issues. This is especially true for some SNARKs relying on elliptic curve pairings, whose security assumptions could similarly be impacted by Shor's algorithm. In contrast, STARKs built on hash functions do not depend on the elliptic curve discrete logarithm assumption, granting them stronger post-quantum security properties.

This means that 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.

According to the timeline, in the protocol priority roadmap released by the Ethereum Foundation in September 2026, it was explicitly stated that efforts will be made to achieve post-quantum resistance on Ethereum L1 across the execution, consensus, and data layers before December 2029. Subsequent upgrade phases will also gradually introduce infrastructure such as post-quantum public key registration, signature verification, consensus proofs, and data commitments.

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

III. How to Safely Migrate Assets for Users?

If the previous sections discussed how Ethereum resolves underlying cryptographic challenges, then what everyday users should focus on most is what our wallets should actually do when the current signature system requires upgrading?

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

The first hurdle to clear is the issue of account identity.

For traditional EOAs, an account address is mathematically tied to a public key. If users directly adopt a new post-quantum key system, they typically must generate a new account identity and then transfer existing assets over.

This creates a cascade of problems. Beyond ETH and ERC-20 tokens, users may hold NFTs, deposits, and positions in DeFi protocols, as well as assets across various L2 networks. Some applications also track permissions, loyalty points, historical interactions, and identity relationships based on the user's address.

If every cryptographic upgrade necessitates changing the account address, users will be forced to manually reconcile these assets and application relationships, resulting in prohibitively high migration costs.

This is where the importance of account abstraction comes into play. It can decouple account identity from underlying signing keys as much as possible, allowing accounts to use programmable verification logic to determine who holds control over assets.

Theoretically, this means users will one day be able to swap out underlying signature algorithms while retaining their original account addresses, avoiding the need to migrate all assets to a new address.

One of the core capabilities EIP-8141 aims to deliver is precisely this.

Secondly, there is the transition between old and new keys. An ideal migration workflow should be initiated by the user proactively authorizing a new post-quantum key to take over the account while the existing cryptographic system remains secure.

For example, a wallet can first generate a new post-quantum key in a secure environment, then use the existing account's valid signature to authorize an update to the account's verification rules.

If the original ECDSA private key remains secure, this process can proceed through a standard account upgrade workflow. But if a quantum computer already possesses the capability to crack existing private keys, the situation changes entirely.

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

And this is precisely why proactive migration is so critical.

Furthermore, there is a more troublesome category of accounts: those that have been unused for long periods, whose private keys are lost, or whose owners are completely unaware that an upgrade is required. These accounts may still hold substantial assets but cannot proactively complete the migration.

Whether these assets should be allowed to remain in their original addresses or if measures like freezing them via protocol governance in the future are warranted remains a subject of debate.

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

As the industry begins discussing quantum threats, attackers will likely exploit user anxiety by creating fake pages purporting to offer «quantum-safe upgrades», «private key verifications», or «asset migrations» to phish for seed phrases or trick users into signing malicious approvals.

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

Conclusion

From today's perspective, quantum computing is still far from reaching a stage where it can directly threaten mainstream blockchain cryptographic systems.

Yet, this does not mean the industry can ignore it.

The post-quantum roadmap Ethereum is advancing essentially demonstrates that future blockchain security should not rest on the assumption that any single cryptographic algorithm will never be broken, but rather on the entire system's capacity for continuous upgrades and secure migration.

For everyday 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, but an evolutionary leap for wallets from private key management tools into long-term asset security management infrastructure.

At least for now, users do not need to hastily migrate assets due to quantum computing. But for wallet developers and the entire crypto industry, the window for proper advance preparation has truly begun.

Прочетете оригинала на Techflowpost

Още новини