Is Crypto Still Safe in the Quantum Computing Era? Insights from Ethereum's Post-Quantum Roadmap

ETH
EIP-8141Post-Quantum CryptographyEthereum RoadmapCryptographic MigrationQuantum Computingaccount abstractionWallet Security
16 hours agoSource: blockweeks.com
Is Crypto Still Safe in the Quantum Computing Era? Insights from Ethereum's Post-Quantum Roadmap

Author: imToken

Quantum computing does not yet pose a real threat, but it is forcing blockchain 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 a public key already exposed on-chain in an extremely short time, would the security system of crypto assets built on cryptography today still hold?

For a long time in the past, discussions about quantum computing in the crypto industry mostly stayed at the level of theoretical speculation, that is, acknowledging that the elliptic curve cryptography widely used by mainstream blockchains such as Bitcoin and Ethereum may be broken in the future by quantum computers with sufficient computing power, but that this is still relatively distant.

In fact, by 2026, this issue has officially entered the engineering implementation stage. The Ethereum Foundation has not only established a dedicated post-quantum security research team, but also set the end of 2029 in its latest protocol roadmap as the engineering goal for L1 to fully achieve post-quantum resistance at 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, replacing the cryptographic system is far from a simple software upgrade.

Especially from the perspective of ordinary users, the real challenge often lies not in "how to generate a new quantum-resistant private key," but in how to still securely and seamlessly control the original accounts and assets during the process of changing signature algorithms.

What does quantum computing really threaten?

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

Currently, Ethereum mainly relies on four types of cryptographic components to operate, serving accounts, consensus, data availability, and application-layer proofs respectively. They solve different problems, and their exposure to quantum computing risks is not equal:

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

Among them, the first to be affected are asymmetric cryptography based on elliptic curve discrete logarithm problems, such as ECDSA and BLS.

As is well known, it is computationally almost infeasible for traditional computers to derive a private key from a public key, but a fault-tolerant quantum computer running Shor's algorithm can theoretically solve the elliptic curve discrete logarithm problem in polynomial time, thereby breaking the security of public key cryptography based on related mathematical assumptions, such as ECDSA and BLS.

Once the private key is restored, an attacker does not need to steal the mnemonic phrase or breach the wallet client, and can directly forge legitimate signatures to transfer assets. Similarly, validator keys, protocol multi-signature management permissions, and cross-chain bridge control keys all face similar long-term tests.

In contrast, hash functions represented by Keccak-256 are more resilient to quantum computing. Although Grover's algorithm can bring a quadratic speedup, it will not directly turn an exponentially hard security problem into a polynomial-time solvable problem like Shor's algorithm.

账户抽象

This also leads to a key detail that is often overlooked: not all Ethereum accounts are at equal risk in the face of quantum threats.

The address of an ordinary Ethereum EOA is obtained by taking the public key, hashing it with Keccak-256, and truncating the result.

Therefore, if one of your cold wallets has never initiated any on-chain transaction externally, nor publicly exposed a signature off-chain, then only the hashed address is recorded on-chain, and the full public key has never been exposed, still protected by the one-wayness of the hash; but as long as that address has initiated even one transfer or contract authorization, an attacker can restore the full public key through the public transaction signature, directly exposing it to the risk of future elliptic curve compromise.

Of course, at this stage, no quantum computer with cryptographic cracking capability has appeared globally, and ordinary users have no need to panic and transfer assets because of this.

The Ethereum Foundation's post-quantum team has also emphasized many times that fault-tolerant quantum computers with actual threats still need to overcome a large number of engineering gaps in hardware scale and quantum error correction (Further reading "What exactly does quantum computing threaten? A Crypto User Guide to the Post-Quantum Era").

But the problem is that cryptographic migration itself takes years, and if we wait until the threat truly appears 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 to coordinate research and engineering implementation of post-quantum cryptography at the protocol layer.

Unlike simply finding a new signature algorithm, Ethereum is trying to advance the upgrade of its cryptographic system simultaneously from three directions: the execution layer, the consensus layer, and the data layer.

账户抽象

Execution layer: making accounts no longer permanently bound to a single private key

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

The account authorization logic of traditional Ethereum EOAs is relatively fixed, that is, users generate signatures through secp256k1 private keys, and the network verifies whether the signature is valid through ECDSA.

This design is simple enough and has been verified over the long term, but it makes the account identity highly bound to a specific signature system. If ECDSA is no longer secure in the future, users will need to change signature algorithms, but simply switching to a new private key often means generating a new account address, and the original assets, contract interaction records, and application relationships may also need to be migrated again.

This is obviously not an ideal solution.

To break this shackle, Ethereum is accelerating the advancement of native account abstraction, the most representative of which is EIP-8141 (Further reading "Native Account Abstraction + Quantum Resistance: Why Has EIP-8141 Not Yet Become the Headliner of Ethereum's Hegotá?").

It attempts to split transaction verification, actual execution, and Gas payment into different execution stages, allowing accounts to determine whether a transaction is valid through programmable logic, thereby helping accounts gradually break free from fixed dependence on ECDSA private keys, achieve native key rotation, and leave room for introducing different signature verification algorithms in the future.

At the same time, Ethereum is also researching post-quantum signature verification precompiles, so that smart contracts and account verification logic can more efficiently natively verify new signature types.

But this is only the first step. Since post-quantum signatures are usually much larger than traditional ECDSA/BLS signatures, Ethereum also needs to address the resulting data and computational cost issues. For example, EIP-8288 proposes using recursive STARK aggregation to compress the verification results of a large number of post-quantum signatures into more compact 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 even more central to the underlying PoS operating mechanism of the Ethereum network.

Currently, PoS consensus relies heavily on the aggregation properties of BLS signatures. If they were directly replaced with ordinary post-quantum signatures, the enormous signature size would significantly increase the costs of P2P network propagation, storage, and verification between nodes.

To this end, Ethereum's Lean Ethereum roadmap has proposed two noteworthy technical directions.

  • leanXMSS: A hash-function-based post-quantum signature scheme, planned to replace the BLS signatures currently used by validators, eliminating the elliptic curve dependency at its root;
  • leanVM: A minimalist zero-knowledge virtual machine designed specifically for efficiently aggregating post-quantum signatures. It attempts to use quantum-resistant zero-knowledge proofs such as recursive STARKs to compress the hash signatures of a large number of validators into compact proofs, thereby safeguarding the bottom line of consensus performance while ensuring quantum-resistant security;

This also shows that there is no one-size-fits-all universal algorithm for the post-quantum upgrade; validator consensus and ordinary user wallets each need to be matched with the cryptographic tools that best suit them.

Data Layer: KZG and ZK Proofs Also Need to Consider Quantum Security

In addition to account signatures and validator signatures, the data layer likewise faces long-term challenges.

In recent years, Ethereum has made extensive use of the KZG polynomial commitment mechanism, especially for Blob and Rollup data availability, and the security of KZG relies on mathematical assumptions related to elliptic curve pairings, so the impact of future quantum computing also needs to be considered.

In addition, at the application layer, some ZK proofs used by systems such as Rollups have similar issues. In particular, some SNARKs that rely on elliptic curve pairings have security assumptions that may likewise be affected by Shor's algorithm; by contrast, STARKs built on hash functions do not rely on the elliptic curve discrete logarithm assumption and therefore have better post-quantum security properties.

This means that the post-quantum migration is not just a problem for Ethereum L1; in the future it will also need to gradually extend to L2, Rollups, and various on-chain applications.

In terms of the timeline, in the protocol priorities published by the Ethereum Foundation in September 2026, it explicitly proposed striving to achieve post-quantum resistance at the execution layer, consensus layer, and data layer of Ethereum L1 before December 2029, and subsequent upgrade milestones 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.

账户抽象

How Can Users Securely Complete Asset Migration?

If the previous two parts discussed how Ethereum can solve the underlying cryptographic problems, then for ordinary users, what is most worth paying attention to is actually when the existing signature system needs to be upgraded, what should our wallets do?

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

The first thing that needs to be solved is the issue of account identity.

For traditional EOAs, there is a direct mathematical association between the account address and the public key. If users directly use a new post-quantum key system, they will usually need to generate a new account identity and then transfer the original assets to it.

But this brings a series of problems. In addition to ETH and ERC-20 tokens, users may also hold NFTs, deposits and positions in DeFi protocols, and assets on different L2 networks. Some applications also record permissions, points, historical interactions, and identity relationships based on user addresses.

If every cryptographic upgrade requires changing the account address, users would have to re-handle these assets and application relationships, and the migration cost would be very high.

Therefore, the importance of account abstraction becomes apparent. It can separate account identity from the underlying signing key as much as possible, allowing accounts to determine who has the right to control assets through programmable verification logic.

In theory, this means that in the future users will have the opportunity to change the underlying signature algorithm while retaining the original account address, without having to move all assets to another address.

This is also one of the capabilities that EIP-8141 hopes to provide.

账户抽象

Second is the migration between old and new keys. An ideal migration process should be when the existing cryptographic system is still secure, the user actively authorizes the new post-quantum key to take over the account.

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

If the original ECDSA private key is still secure, this process can proceed according to the normal account upgrade process. But if quantum computers already have the ability to crack existing private keys, the situation is completely different.

At that point, both attackers and the real user may have the ability to forge signatures for the original account, and it will be very difficult for the system to determine, based solely on the old key, who the legitimate owner really is.

This is also why migrating in advance is so important.

In addition, there is another type of even trickier account: wallets that have not been used for a long time, whose private keys have already been lost, or whose owners simply do not know that an upgrade is needed. These accounts may still hold large amounts of assets but are unable to actively complete migration.

For such assets, whether they should be allowed to remain at the original addresses, or whether measures such as freezing should be taken in the future through protocol governance, remains controversial.

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

When the entire industry begins discussing the quantum threat, attackers are very likely to exploit users' panic to create so-called "quantum security upgrade," "private key verification," or "asset migration" pages, tricking users into entering mnemonic phrases or signing malicious authorizations.

Therefore, future wallets must not only provide migration tools, but also enable users to clearly identify the source of upgrades, verify transaction contents, and confirm exactly which assets the new authorization logic controls.

账户抽象

Final Thoughts

As things stand today, quantum computing is still far from reaching the level where it can directly threaten the cryptographic systems of mainstream blockchains.

But this does not mean the industry can ignore it.

The post-quantum roadmap that Ethereum is advancing actually also shows that the future of blockchain security should not be built on the assumption that a certain cryptographic algorithm will never be broken, but should be built on the ability of the entire system to continuously upgrade and securely migrate.

For ordinary users, the role of wallets will also change as a result.

In the past, the core job of a wallet was to help users generate, safeguard, and use private keys; in the future, it will also need to help users understand account risks, manage keys under different cryptographic systems, and securely complete account upgrades when necessary.

This is not just a change of signature algorithm, but an evolution of the wallet from a private key management tool into infrastructure for long-term asset security management.

At least today, users do not yet need to rush to migrate assets because of quantum computing, but for wallet developers and the entire crypto industry, the time that is truly worth preparing in advance has already begun.