Ethereum co-founder Vitalik Buterin has thrown his weight behind leanPCS, calling it a faster route to quantum-safe Ethereum. The approach would let ETH▼$1,802.78 wallets adopt larger, quantum-resistant signatures by bundling their verification into a shared proof, keeping the extra data off permanent chain storage.

His endorsement, published November 16, 2026, confronts a concrete size problem: a standard Ethereum signature occupies 65 bytes, while some quantum-resistant alternatives require about 1,000–6,000 bytes. Standardizing a smaller checking tool, Buterin argues, could let developers introduce proof aggregation sooner than a broader overhaul would allow.

Buterin Backs leanPCS as Ethereum Weighs Quantum Defenses

What changed in Buterin’s assessment of leanPCS?

“Over the past few weeks I’ve gone from thinking leanPCS is total bull to being a total bull,” Buterin wrote on X, per CoinDesk. The reversal centers on a proposed path to shared verification that still leaves proof-system developers room to make their own design choices.

Related: Two Ethereum Proposals Aim to Protect 200,000 Contracts From Glamsterdam

Buterin now backs leanPCS as a way to standardize one small mathematical checking tool. Different proof systems could share that tool while building the rest of their architecture however they like. The benefit to users, if implemented, would flow through stronger wallet security and lower transaction costs.

Why is the proposal getting attention now?

The endorsement lands days after researchers pushed to prioritize quantum defenses over faster blocks in Ethereum’s planned 2027 upgrade. That framing puts leanPCS inside an active argument about what gets development attention first.

EIP-8288 is still a draft, and its published specification lists the reference implementation as unfinished. Buterin’s support adds a prominent advocate, but finishing the implementation and winning the upgrade-priority debate are what actually move it forward.

How EIP-8288 Would Combine Ethereum Signatures and Proofs

What happens between a wallet signature and the shared proof?

A wallet would still produce a signature proving its owner authorized a payment. Computers receiving that signature would combine its verification with checks on other signatures and application proofs before anything reaches the blockchain. Those batches would then be combined again, eventually collapsing into one mathematical proof confirming all the included checks passed.

That repeated aggregation is the core mechanism. Without it, every bulky signature becomes its own permanent storage burden.

What would Ethereum verify at the block level?

A block would carry the shared proof alongside payment instructions and the data needed to check it. Ethereum would verify the combined result without permanently storing every individual signature.

LeanPCS addresses the specific tool that different proof systems would share within that workflow. Wallets get stronger signatures; aggregation contains the storage cost of using them.

Buterin’s Proposal Leaves Proof-System Developers More Choices

Who would build and perform the proposed aggregation?

Computers receiving wallet-generated signatures would handle aggregation, combining signature checks with other proofs and repeatedly merging the resulting batches before transactions reach the chain. Buterin is advocating the approach and explaining its tradeoffs; proof-system developers would build around the shared checking tool while making their own decisions about everything surrounding it.

Why avoid an early commitment to a new computing language?

The broader alternative would require Ethereum developers to agree on a new computing language for programs whose work the network verifies. Buterin describes that as a substantial commitment because changing the language later would be difficult.

LeanPCS narrows the agreement to one smaller mathematical component, which he argues could deliver similar flexibility sooner. The tradeoff is more information onchain compared with the broader alternative — some storage efficiency exchanged for a faster path through a consequential design decision.

Ethereum’s Earlier Quantum Roadmap Set Up the Aggregation Push

How did the earlier roadmap connect wallet changes and aggregation?

In its February 27 coverage, crypto.news described a phased quantum-resistance roadmap covering Ethereum’s consensus layer, data availability, wallets and application proofs. Proposed replacements included hash-based or lattice-based cryptography, supported by recursive STARK aggregation. That earlier plan already paired stronger cryptography with a mechanism to manage its larger signatures, and identified native account abstraction under EIP-8141 as the route for wallets to adopt post-quantum schemes once efficient implementations arrive.

How does leanPCS fit the broader Lean Ethereum direction?

July coverage by CryptoBriefing placed quantum safety rising on Ethereum’s roadmap, alongside operational simplification and statelessness. The leanPCS endorsement narrows that larger picture to one design choice: how to introduce flexible proof verification without waiting for consensus on a full new computing language. EIP-8288 is where those broader priorities become a specific engineering proposal.

Ethereum’s Signature Problem Runs From 65 to 6,000 Bytes

How much larger are the proposed signature alternatives?

Against the 65-byte standard, a 1,000-byte alternative is roughly 15 times as large. At 6,000 bytes, the upper end is roughly 92 times as large. If Ethereum permanently retained each oversized signature, the block space consumed would push up the fees users pay to transfer tokens or interact with applications.

How does aggregation address that storage pressure?

The proposal shifts the permanent record toward payment instructions and a shared verification result. Computers process individual signatures before the block reaches the chain, so the final proof stands in for the separate checks. For ETH users, that means stronger wallet authorization without paying to store every large signature individually — though how much it helps depends on the aggregation system developers actually build.

Privacy Benefits Come With a leanPCS Storage Tradeoff

Why could Ethereum privacy applications benefit?

Privacy applications also rely on mathematical proofs, and those proofs grow under stronger cryptographic approaches. The same aggregation process could bundle them alongside wallet checks, extending the storage benefit beyond payments. Developers building privacy tools would have a practical reason to support shared verification, not just wallet-security advocates.

What technical risks and costs remain?

Quantum computers powerful enough to break current cryptography could forge signatures and compromise wallets — the threat the earlier roadmap was designed to preempt. Replacing vulnerable cryptographic components is one part of the response; making their verification affordable is the other.

LeanPCS carries a continuing data cost: it puts more information onchain than the alternative that requires agreeing on a new computing language. Developers would have to weigh that tradeoff against the flexibility and earlier introduction Buterin believes the smaller tool could offer.

What to Watch in EIP-8288 Development and the 2027 Debate

Which development milestone matters next for quantum-safe Ethereum?

The unfinished reference implementation is the concrete piece of work to follow. Completing it moves EIP-8288 past a draft specification and gives developers something to build and argue around. The underlying engineering choice — how much Ethereum standardizes now versus how much it leaves to individual proof systems — will drive that work.

How does the 2027 upgrade discussion affect priorities?

Researchers’ push to favor quantum defenses over faster blocks puts security work in direct competition with an improvement users would feel immediately. The planned 2027 upgrade is where that priority call gets made. EIP-8288 is one piece of the security side of that argument.

The developments worth tracking are progress on the reference implementation, the choice of verification framework, and where quantum defenses land in upgrade planning. Those decisions will determine how Ethereum pursues stronger wallet protection while keeping the cost of larger signatures manageable.

FAQ

How large is a standard Ethereum transaction signature?

The standard signature occupies 65 bytes. That figure covers the signature authorizing the transaction, not the complete transaction and its other instructions.

How large are the quantum-resistant signature alternatives cited by Buterin?

Some alternatives require about 1,000–6,000 bytes, according to Buterin’s figures. Their larger storage footprint is precisely why his proposal pairs stronger signatures with shared verification.

What information would Ethereum keep onchain under the proposed aggregation system?

Ethereum would retain payment instructions and enough data to verify a shared mathematical proof. The block could confirm all included checks passed without permanently holding every bulky signature separately.

Which applications besides wallet payments could benefit from proof aggregation?

Privacy applications are another intended beneficiary because their mathematical proofs can also expand under stronger cryptography. Combining those proofs could reduce the amount of proof data each user must pay to store individually.

What role does EIP-8141 play in the earlier quantum-resistance roadmap?

EIP-8141 would introduce native account abstraction, giving wallets a path to adopt post-quantum signature schemes. The earlier roadmap ties that transition to the availability of efficient implementations.

Which four parts of Ethereum did the earlier quantum roadmap identify as vulnerable?

The roadmap identified consensus-layer BLS signatures, data availability using KZG commitments, wallet signatures using ECDSA, and application proofs such as Groth16. Its proposed transition reaches across all four areas.

What longer upgrade horizon did the earlier Strawmap describe?

According to CryptoBriefing’s July coverage, the Strawmap described approximately seven anticipated hard forks spanning 2026 through 2030, spreading the broader transformation across multiple upgrades.

This article is for information only and is not financial advice.

Tom Lee Ether Price Prediction Has No Target as ETH Trades at $2,244

The Tom Lee Ether price prediction search turns up no documented target; Ethereum’s ETH traded at...

BitMine Accelerates Ethereum Purchases, Boosts Reserves to 4.8 Million ETH

Over the past week, BitMine Immersion Technologies acquired 71,252 ETH▼$1,802.78. This marks the...

Google Warns Quantum Risk to Bitcoin and Ethereum Is Closer Than Thought

The tech giant says the keys behind Bitcoin and Ethereum are closer to breakable than many thought....

Ethereum ETF Update: Could Staking ETFs Become ETH’s Biggest Catalyst?

Ethereum ETF update coverage is no longer only about inflows and outflows. The bigger question is...

Coldcard Hardware Bitcoin Wallet Bug Puts Years of BTC Seeds at Risk

Coldcard users are being urged to move their Bitcoin to newly generated wallets over a security...

BitMine’s Tom Lee Explains Why ETH Price Is Falling — But Continues Buying Ethereum

Tom Lee believes Ethereum’s price is dropping due to “window dressing.” Still, his company...