Ethereum tests quantum-safe signatures that increase size and CPU

Ethereum core developers and client teams are testing quantum-safe signature schemes and prototype transaction formats on public testnets and in client branches. The work aims to protect private keys from potential future quantum attacks while keeping existing elliptic-curve accounts compatible.

Teams are evaluating algorithms that resist attacks by quantum computers, focusing mainly on lattice-based and hash-based schemes that cryptography authorities have standardized or recommended. Those schemes produce larger signatures and keys and require more CPU cycles to verify than the secp256k1 and BLS signatures currently used on Ethereum.

Engineers are introducing the changes in stages. Client maintainers are adding optional signature types and experimental APIs so wallets and validators can create and check quantum-resistant signatures without forcing an immediate network-wide switch. Some implementations target the consensus layer first, where validator signatures are aggregated, while others enable new transaction types on execution-layer testnets.

The main technical effects are higher bandwidth and greater compute demand. Larger signatures increase the byte size of transactions stored in blocks and transmitted across the peer-to-peer network. Heavier verification work raises CPU load during node synchronization and block validation, which can be significant on resource-constrained hardware. Some teams are testing hybrid signatures that include both classical and post-quantum components; hybrids raise sizes and verification effort further because clients must validate two signature schemes per operation.

Those changes could alter how many transactions fit in a block and how clients charge for signature verification. Bigger signatures consume more block space, which can reduce transaction throughput unless block gas limits or fee structures are adjusted. Higher verification costs may lead clients and protocol designers to revise gas charges for signature checks. Layer-2 systems, bridges, hardware wallets and custody services must update verification logic and key-management tools to handle the new formats.

Development and deployment are being coordinated through the Ethereum Improvement Proposal process and client release notes. Testnets are being used to collect empirical data on block propagation times, state growth and transaction fees under different activation scenarios. The testing period is intended to inform choices about which algorithms to support, whether to use hybrid approaches and how to price verification in gas accounting.

The push toward quantum-resistant cryptography follows concern that a sufficiently large, fault-tolerant quantum computer could run algorithms such as Shor’s to break widely used elliptic-curve cryptography and expose private keys. Standards bodies have advanced post-quantum algorithms, and multiple software projects are planning transitions to avoid urgent migration later.

Node operators, wallet developers and custodial services face operational work during the transition. Operators may need more powerful hardware to handle verification load. Custodians will need plans to rekey accounts securely. Wallet vendors must implement new key formats and provide clear migration steps for users. Until a formal activation plan is chosen, the network will run experiments to measure performance and finalize migration timelines and gas pricing decisions.