Author: imToken
Quantum computing does not yet pose a real threat, but it is pushing blockchains to redesign account authorization, key management, and asset migration mechanisms.Article by: imToken
If one day a quantum computer could derive private keys from publicly exposed public keys on the blockchain in an extremely short time, would today’s cryptographic foundation for securing digital assets still hold?
For a long time, discussions in the crypto industry about quantum computing remained largely theoretical, acknowledging that elliptic curve cryptography, widely used by major blockchains like Bitcoin and Ethereum, could potentially be broken by quantum computers with sufficient computing power—but this scenario is still quite distant.
In fact, by 2026, this issue had officially entered the phase of engineering implementation, with the Ethereum Foundation not only establishing a dedicated post-quantum security research team but also setting the end of 2029 as the engineering target for full post-quantum resistance across the execution, consensus, and data layers of L1 in its latest protocol roadmap.
For an open network with hundreds of millions of accounts, massive asset holdings, and a complex application ecosystem, changing the cryptographic system is far more than a simple software upgrade.
Especially from the perspective of an ordinary user, the real challenge is not about "how to generate a new quantum-resistant private key," but rather how to securely and seamlessly maintain control over existing accounts and assets during the transition to a new signing algorithm.
What does quantum computing truly threaten?
To understand the impact of quantum computing on crypto assets, first break down the blockchain security system.
Ethereum currently relies on four categories of cryptographic components to operate, serving accounts, consensus, data availability, and application-layer proofs respectively; each addresses distinct problems and has varying levels of exposure to quantum computing risks:
- ECDSA: The elliptic curve digital signature algorithm used for ordinary user accounts to prove ownership of the transaction initiator;
- BLS: A signature algorithm used in Ethereum's PoS consensus layer that efficiently aggregates votes from hundreds of thousands of validators into a single signature;
- ZK-proof systems: Zero-knowledge proof systems used in applications such as Rollups;
- KZG: A polynomial commitment scheme used for Blob and Rollup data availability (DA) verification;
Among these, the foremost are asymmetric cryptographic systems such as ECDSA and BLS, which are based on the elliptic curve discrete logarithm problem.
It is well known that classical computers find it computationally infeasible 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 compromising the security of public-key cryptography such as ECDSA and BLS, which rely on these mathematical assumptions.
Once the private key is recovered, attackers can directly forge legitimate signatures to transfer assets without stealing the mnemonic phrase or compromising the wallet client; similarly, validator keys, protocol multisig management permissions, and cross-chain bridge control keys also face similar long-term risks.
In comparison, hash functions such as Keccak-256 are more resilient to quantum computing. While Grover’s algorithm can provide a quadratic speedup, it does not transform the problem from exponentially secure to polynomial-time solvable, as Shor’s algorithm does.

This also highlights a key detail often overlooked: not all Ethereum accounts are equally at risk from quantum threats.
The address of a standard Ethereum EOA is derived by taking the Keccak-256 hash of the public key and truncating it.
Therefore, if your cold wallet has never initiated any on-chain transaction and has never publicly disclosed a signature off-chain, the on-chain record will contain only the hashed address—the full public key has never been exposed and remains protected by the one-way nature of hashing; however, as soon as that address initiates even a single transfer or contract authorization, an attacker can reconstruct the full public key from the publicly available transaction signature, exposing it to the risk of future elliptic curve breakthroughs.
Currently, no quantum computer capable of cryptanalysis exists globally, so ordinary users have no need to panic and transfer their assets.
The Ethereum Foundation’s post-quantum team has also repeatedly emphasized that a fault-tolerant quantum computer posing a real threat still needs to overcome significant engineering challenges in hardware scale and quantum error correction (see further reading: “What Exactly Does Quantum Computing Threaten? A Crypto User’s Guide to the Post-Quantum Era”).
But the problem is that 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 to coordinate research and engineering implementation of post-quantum cryptography at the protocol level.
Instead of simply seeking a new signature algorithm, Ethereum is simultaneously advancing its cryptographic system across three layers: execution, consensus, and data.

Execution layer: Decouple accounts from permanent binding to a single private key
For ordinary users, the most direct changes come from the execution layer.
The account authorization logic of traditional Ethereum EOA is relatively fixed: users generate signatures using secp256k1 private keys, and the network verifies the validity of the signatures using ECDSA.
This design is simple and has been proven over time, but it tightly binds account identity to a specific signing system. If ECDSA becomes insecure in the future, users will need to switch signing algorithms; however, simply generating a new private key often means creating a new account address, requiring the migration of existing assets, contract interaction histories, and application relationships.
This is clearly not an ideal solution.
To break this constraint, Ethereum is accelerating the adoption of native account abstraction, with EIP-8141 being the most prominent example (see further reading: Native Account Abstraction + Quantum Resistance: Why Isn’t EIP-8141 Ethereum’s Hegotá Headliner?).
It attempts to separate transaction validation, actual execution, and Gas payment into distinct execution steps, allowing accounts to use programmable logic to determine whether a transaction is valid, thereby helping accounts gradually reduce their fixed reliance on ECDSA private keys, enable native key rotation, and leave room for introducing different signature verification algorithms in the future.
Meanwhile, Ethereum is also researching post-quantum signature verification precompiles to enable smart contracts and account validation logic to natively verify new signature types more efficiently.
But this is only the first step. Since post-quantum signatures are typically much larger than traditional ECDSA/BLS signatures, Ethereum also needs to address the resulting data and computational costs. For example, EIP-8288 proposes using recursive STARK aggregation to compress the verification results of many post-quantum signatures into a more compact proof, thereby reducing on-chain data and verification overhead.
Consensus layer: Replace traditional BLS with hash signatures
Beyond the execution layer, the consensus layer is fundamental to Ethereum network’s underlying PoS mechanism.
Currently, PoS consensus heavily relies on the aggregation property of BLS signatures; directly replacing them with conventional post-quantum signatures would significantly increase P2P network propagation, storage, and verification costs due to the large signature sizes.
To this end, the Lean Ethereum roadmap proposes 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 their source;
- leanVM: A minimalist zero-knowledge virtual machine designed for efficient aggregation of post-quantum signatures, aiming to compress hash signatures from numerous validators into compact proofs using quantum-resistant zero-knowledge proofs such as recursive STARKs, while maintaining consensus performance and ensuring post-quantum security;
This also shows that there is no one-size-fits-all algorithm for post-quantum upgrades; validator consensus and regular user wallets each require cryptographic tools best suited to their specific needs.
Data layer: KZG and ZK proofs also need to consider quantum security.
In addition to account signatures and validator signatures, the data layer also faces long-term challenges.
Ethereum has widely adopted the KZG polynomial commitment scheme in recent years, particularly for blobs and rollup data availability. The security of KZG relies on mathematical assumptions related to elliptic curve pairings, and thus the potential impact of future quantum computing must also be considered.
Additionally, at the application layer, certain ZK proofs used by systems like Rollups face similar issues, particularly some SNARKs that rely on elliptic curve pairings, whose security assumptions may also be compromised by Shor’s algorithm; in contrast, STARKs built on hash functions do not depend on the elliptic curve discrete logarithm assumption and therefore offer superior post-quantum security properties.
This means that post-quantum migration is not just an issue for Ethereum L1—it will also need to be gradually extended to L2s, Rollups, and various on-chain applications.
According to the roadmap, the Ethereum Foundation explicitly aims to achieve post-quantum resistance on Ethereum L1 at the execution, consensus, and data layers by December 2029, as outlined in its protocol priorities announced in September 2026. Subsequent upgrades will gradually introduce post-quantum infrastructure, including 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 first two parts discussed how Ethereum addresses underlying cryptographic challenges, what matters most to everyday users is how our wallets should respond when the existing signature system needs an upgrade.
This is much more complex than simply regenerating a private key.
The first issue to address is account identity.
For traditional EOA accounts, the account address is directly mathematically linked to the public key; if users adopt a new post-quantum key system, they typically need to generate a new account identity and transfer their existing assets to it.
However, this raises a series of issues. 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 each cryptographic upgrade required changing account addresses, users would have to reconfigure their asset and application relationships, resulting in very high migration costs.
Therefore, the importance of account abstraction becomes evident, as it separates account identity from the underlying signing keys, allowing accounts to determine who has authority to control assets through programmable verification logic.
Theoretically, this means users will have the opportunity in the future to switch the underlying signing algorithm while retaining their existing account addresses, without needing to move all assets to another address.
This is also one of the capabilities EIP-8141 aims to provide.

Second, it is the migration between old and new keys. An ideal migration process should involve users proactively authorizing new post-quantum keys to take over their accounts while the existing cryptographic system remains secure.
For example, a wallet can first generate a new post-quantum key in a secure environment, then authorize the update of the account’s verification rules using a valid signature from the existing account.
If the original ECDSA private key is still secure, this process can proceed according to the standard account upgrade procedure; however, if quantum computers have already gained the capability to break existing private keys, the situation is entirely different.
At this point, both the attacker and the legitimate user may possess the ability to forge signatures from the original account, making it difficult for the system to determine the true owner based solely on the old key.
This is why migrating early is so important.
In addition, there is another category of more challenging accounts—those that have been inactive for a long time, have lost their private keys, or whose owners are unaware that an upgrade is required. These accounts may still hold significant assets but are unable to initiate the migration.
There is still debate over whether such assets should be allowed to remain in their original addresses or whether measures such as freezing should be taken in the future through protocol governance.
Finally, and most easily overlooked, is that the migration itself must not become a new entry point for attacks.
As the entire industry begins discussing quantum threats, attackers are likely to exploit users' panic by creating fake pages claiming to offer "quantum-safe upgrades," "private key verification," or "asset migration," tricking users into entering their seed phrases or signing malicious approvals.
Therefore, future wallets must not only provide migration tools but also enable users to clearly identify the source of the upgrade, verify transaction details, and confirm which assets are controlled by the new authorization logic.

In conclusion
From today’s perspective, quantum computing is still far from being able to directly threaten mainstream blockchain cryptographic systems.
But that doesn't mean the industry can ignore it.
Ethereum’s post-quantum roadmap demonstrates that future blockchain security should not rely on the assumption that any single cryptographic algorithm will never be broken, but rather on the system’s ability to continuously upgrade and securely migrate.
For ordinary users, the role of wallets will also change accordingly.
In the past, the core function of a wallet was to help 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 securely perform account upgrades when necessary.
This is not merely a change in signature algorithm, but an evolution of the wallet from a private key management tool into a long-term asset security infrastructure.
At least for today, users do not need to rush to migrate their assets due to quantum computing, but the time for wallet developers and the entire crypto industry to prepare in advance has already begun.





