EL7.AI
CryptoMedium•16 November 2026•
4 min read

Buterin Turns Optimistic on leanPCS Amid Ethereum Proof Aggregation Debate

Key Facts

1Buterin shifted from strong skepticism to optimism about leanPCS.
2Direct verification of hash-based signatures may require 150,000 to 200,000 gas units.
3STARK proofs may reach 512 kilobytes when optimized for faster generation.
4Ethereum is targeting quantum resistance across its three layers by December 2029.

Vitalik Buterin has shifted from strong skepticism to optimism about leanPCS, according to a report today on the evolution of his views. This coincides with a separate draft, EIP-8288, authored by Buterin and Thomas Kötterg, titled "Aggregating Signatures and Proofs Inside the Transaction Pool." The published proposal specification is classified as a draft proposal and does not mention leanPCS. The proposal aims to aggregate cryptographic signatures and STARK proofs in a recursive structure, including for privacy protocol use cases. But the proposal has not become an activated network change, and the specification does not establish a realized improvement in Ethereum's efficiency on the live network.

The draft explains that EIP-8288 extends EIP-8141 by adding a new frame mode that allows cryptographic signatures and STARK proofs to be aggregated at the Ethereum Virtual Machine level. This places the proposal on a specific technical path: combining verification evidence into a recursive proof rather than handling each signature and proof separately. Its motivations include data sizes that may accompany quantum-resistant signatures and zero-knowledge proofs. The specification states that hash-based signatures under consideration may range in size from 2 to 3 kilobytes, and that verifying them directly may cost 150,000 to 200,000 gas units. STARK proofs, meanwhile, exceed 128 kilobytes and may reach 512 kilobytes when faster generation is prioritized.

Under the proposed design, transaction pool nodes aggregate proofs recursively, then broadcast an aggregation wrapper every 1000 milliseconds. When transactions are included in a block, the block does not carry every signature and proof submitted by the user directly; instead, it carries a single recursive STARK proof establishing the presence of those elements and the validity of the dependencies among them. The specification says this arrangement is intended to handle large cryptographic data by combining it into a unified proof. This description concerns EIP-8288's mechanism itself; it does not provide a technical specification for leanPCS or evidence that the two technologies are part of one proposal. Buterin's reported optimism about leanPCS therefore remains a shift in his position, while the published proposal remains a separate draft design.

Ethereum's broader roadmap links research into aggregation with the shift to quantum-resistant cryptography, while using different tools and proposals. According to Ethereum.org, moving from BLS signatures to hash-based leanXMSS signatures increases the approximate size from 96 bytes to 3,000 bytes, while the page describes leanVM as compressing data by a factor of 250. The comparison explains why aggregation has been proposed to reduce the data burden, but it does not mean that leanPCS is leanVM or that its compression is part of EIP-8288. The page also says the Ethereum Foundation formed a dedicated post-quantum security team in January 2026, led by Thomas Kötterg, one of the proposal's authors. In March 2026, Google Quantum AI research, as cited by Ethereum.org, estimated that breaking 256-bit elliptic-curve cryptography could require about 1,200 logical qubits, while noting that the quantum threat is not imminent.

In its 2026 protocol priorities update, the Ethereum Foundation said proposals were in development to make verification of quantum-resistant signatures inside the Ethereum Virtual Machine less gas-intensive. A later update from the protocol team set a goal of making all three network layers—execution, consensus and data—quantum-resistant by December 2029. The foundation said in September 2026 that client teams could realistically begin implementing Hegotá in late Q4 2026. But it described the schedule for full readiness by December 2029 as ambitious, requiring an average pace of 7.2 months per upgrade from Glamsterdam to L*. EIP-8288 remains one of the drafts that would require an adoption path and a network upgrade before becoming part of the protocol.

The EIP-8288 page says the proposal was created on 3 June 2026 and requires EIP-2718 and EIP-8141. It also states that its implementation would require a network upgrade, because nodes that do not include the change would reject blocks carrying the proposed recursive STARK header field. Its impact therefore goes beyond changing how an individual application displays or calculates data, as it concerns block acceptance rules between nodes. The specification has not set an activation date in the published information. The leanPCS track remains separate in this context, with the reported development limited to Buterin's shift from skepticism to optimism.

Open on chart