Crypto News

Vitalik Backs leanPCS to Cut Ethereum's Quantum-Security Costs

Published: Nov 16, 2026•By Aleksandar Dukic

Key Analysis

Vitalik Buterin backs leanPCS to aggregate quantum-resistant proofs on Ethereum, targeting lower data costs while the wider protocol upgrade remains a draft.

Vitalik Backs leanPCS to Cut Ethereum's Quantum-Security Costs

Listen To This Article

Vitalik Backs leanPCS to Cut Ethereum's Quantum-Security Costs

4m 51s audio

AI narration. Useful for scanning on the move. Names and tickers may be mispronounced.

Vitalik Buterin is backing leanPCS as an approach to handling the larger cryptographic proofs that a quantum-resistant Ethereum would need. CoinDesk's November 16 report describes a system that combines bulky verification work before it reaches the blockchain, aiming to avoid passing the full storage burden to users.

The attraction is straightforward: stronger signatures become easier to accommodate if Ethereum can verify them collectively. But "zero fee burden" overstates the result. The related aggregation proposal, EIP-8288, remains a draft and includes gas charges. Buterin's endorsement concerns a development approach, rather than an activated upgrade or a promise about transaction prices.

Larger signatures create a capacity problem

Ethereum's quantum-security work has two connected tasks: changing vulnerable cryptography and keeping the replacement practical to run.

The Ethereum Foundation's post-quantum team explains that a sufficiently powerful quantum computer could recover private keys from exposed public keys, allowing forged signatures. For users, the prospective danger is someone authorizing new transactions with their funds. The team does not consider such a machine imminent, but says migrating a decentralized protocol requires years of engineering and coordination.

Replacement algorithms already exist beyond Ethereum. NIST's ML-DSA standard specifies a digital signature system believed to resist attacks even from a large quantum computer. Its purpose remains familiar: authenticate the signer and detect unauthorized changes to signed data.

An algorithm's security properties, however, answer a different question from whether a busy blockchain can afford to process it transaction by transaction.

EIP-8288 describes proposed hash-based signatures of roughly 2 to 3 kilobytes, with individual verification costs around 150,000 to 200,000 gas. The draft uses those estimates to explain the proposal's rationale.

The economic problem follows from that design: carrying and verifying a large signature separately for each user would consume resources that aggregation could share.

Verification moves into a shared proof

The mechanism described in CoinDesk's announcement combines bulky proofs into a compact proof before they reach the blockchain. That changes the amount of evidence Ethereum needs to retain for each individual check.

Under EIP-8288, transactions declare cryptographic dependencies. Participants aggregate the supporting signatures and proofs outside the chain, producing a recursive STARK, a mathematical proof that covers the required checks. A block must contain a valid aggregate proof.

"Recursive" describes the batching process: proofs can cover earlier proofs, allowing several rounds of aggregation before the final result reaches a block.

The transaction instructions still matter. Combining evidence that a payment was authorized does not eliminate the payment itself. Ethereum still needs enough information to execute transactions and verify the aggregate result. The proposed saving comes from handling the supporting cryptography collectively, reducing the verification evidence accompanying those instructions.

As an engineering judgment, this targets a more useful objective than simply choosing a replacement signature: it addresses the cost of using that signature repeatedly across a network. A signature system must be practical both for an individual transaction and for the volume of checks Ethereum needs to perform.

Lower overhead still requires engineering work

CoinDesk frames leanPCS as a way to make quantum defenses practical without increasing fees or block-space usage. That is the ambition motivating the endorsement. The draft's explicit gas accounting describes how aggregation would charge for the work involved while aiming to reduce the overhead of stronger cryptography.

A shared proof still has to be produced and checked. Aggregation changes how that work is distributed and charged.

An efficient design could reduce the penalty associated with larger signatures, while the eventual user fee would depend on the implemented protocol and its resource charges. The economic question is how much shared verification saves once those costs are included.

The Foundation's broader plan also spans several parts of Ethereum. Its post-quantum team describes work on account authentication, validator signatures and data availability. It favors gradual account migration through account abstraction, alongside separate changes elsewhere in the protocol.

For people managing their own keys, the practical consequence is that quantum resistance involves both network upgrades and account support. A proof-aggregation technique addresses the cost of checking authentication evidence; account migration remains another part of the transition.

The research deserves attention for its specific target: accommodating stronger authentication without requiring every transaction to bear the full cost of its cryptographic evidence. Making that evidence cheaper to handle would help with the transition, alongside the migration work across Ethereum's accounts and wider protocol.

Overview

Buterin's support puts leanPCS behind a concrete Ethereum engineering objective: aggregate larger signatures and proofs before their full data burden reaches the chain.

Shared verification could make quantum-resistant transactions more economical. Ethereum's broader transition still requires changes across accounts, consensus and data handling. EIP-8288 sets out a proposed approach to aggregation and explicit gas accounting within that larger effort.

DisclaimerThis article is provided for informational purposes only and does not constitute financial advice. All fee, limit, and reward data is based on issuer-published documentation as of the date of verification.

Have a question or update?

Discuss this analysis with the community on X.

Discuss on X

Comments

Comments are moderated and may take a moment to appear.