Ethereum Quantum-Safe Upgrade Gets Vitalik’s leanPCS Backing
Ethereum’s quantum-safe upgrade may have found a faster route forward, but the technical work isn’t finished.
Vitalik Buterin has shifted his support toward leanPCS under EIP-8288, arguing it could deliver much of leanSTARK’s flexibility without forcing developers to standardize a new instruction-set architecture first.
That’s a significant change in direction. It isn’t a completed upgrade, though.
EIP-8288 Still Has Important Development Gaps
EIP-8288 aims to reduce the amount of cryptographic data Ethereum must carry on-chain. Instead of publishing every signature or proof, nodes aggregate verification results into STARK proofs, which can then be aggregated further.

The chain ultimately receives compact claims and a master proof, rather than every underlying cryptographic object.
The motivation is becoming harder to ignore. Current 65-byte ECDSA signatures could grow to 1–6 kilobytes under proposed quantum-safe schemes.
Meanwhile, zero-knowledge proofs could expand from roughly 200–1,000 bytes to around 128 kilobytes when using STARKs. Putting all that data on-chain isn’t a practical scaling strategy.
Why leanPCS Could Speed Up Quantum-Safe Ethereum
Buterin’s latest explanation separates three approaches. leanSPHINCS supports a specific hash-based signature scheme, offering quantum-safe accounts with a proposed cost of 4,096 gas for 64 bytes.
leanSTARK is more flexible. Users could prove almost any computation, but Ethereum would first need to agree on a programming language or instruction-set architecture. That’s a difficult standard to lock in.
leanPCS offers a middle path. A polynomial commitment scheme proves a statement about a polynomial, and Buterin estimates STARK verification through this mechanism could cost around 20,000–40,000 gas.
It may require more claims on-chain than leanSTARK. In exchange, developers retain greater flexibility over off-chain proof systems.
Ethereum’s Quantum-Safe Upgrade Still Needs Implementation
The published EIP-8288 draft currently specifies leanSPHINCS and reserves leanSTARK, while leanPCS isn’t yet included as a verification mode. Its reference implementation remains listed as TBD, and no activation date is confirmed.
That gap matters. An endorsement isn’t a specification, and a specification isn’t a working network upgrade.
For now, Ethereum’s quantum-safe upgrade has a potentially faster technical direction, but leanPCS still needs formal integration, implementation and approval before it can become part of the network.
Was this writing helpful?
Story Ends Here
Trust with CoinPedia:
CoinPedia has been delivering accurate and timely cryptocurrency and blockchain updates since 2017. All content is created by our expert panel of analysts and journalists, following strict Editorial Guidelines based on E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness). Every article is fact-checked against reputable sources to ensure accuracy, transparency, and reliability. Our review policy guarantees unbiased evaluations when recommending exchanges, platforms, or tools. We strive to provide timely updates about everything crypto & blockchain, right from startups to industry majors.
Investment Disclaimer:
All opinions and insights shared represent the author’s own views on current market conditions. Please do your own research before making investment decisions. Neither the writer nor the publication assumes responsibility for your financial choices.
Sponsored and Advertisements:
Sponsored content and affiliate links may appear on our site. Advertisements are marked clearly, and our editorial content remains entirely independent from our ad partners.
Read the Next News
