Ethereum: Vitalik Buterin is now banking on leanPCS to accelerate quantum resistance
Summarize this article with:

On November 16, 2026, Vitalik Buterin announced support for leanPCS, an approach intended to facilitate the aggregation of cryptographic proofs on Ethereum. It aims to prepare the network for signatures resistant to quantum computers, of up to 6,000 bytes compared to 65 today, without making each block heavier. L’EIP-8288 However, it remains a draft without a timetable and does not yet mention leanPCS.

Vitalik Buterin holds a glowing cryptographic device in front of a gigantic mechanical eye symbolizing the threat of quantum computers, while the Ethereum logo is protected by an orange energy shield.

In brief

  • On November 16, Vitalik Buterin said he supported leanPCS, which he previously rejected.
  • Some quantum signatures would weigh 1,000 to 6,000 bytes, compared to 65 today.
  • EIP-8288 offers a recursive STARK proof aggregating checks before including them in bulk.
  • The draft does not mention leanPCS or set a date.

Vitalik Buterin supports leanPCS to contain the weight of quantum signatures

In a post published on X on November 16, 2026, Ethereum co-founder Vitalik Buterin writes having gone from the idea that leanPCS is “total bull” to that of being “a total bull” in recent weeks.

leanPCS is based on a polynomial commitment scheme (PCS, for Polynomial Commitment Scheme). This is the central mathematical building block of STARK proofs. It would standardize a small verification tool that different proof systems could use. Buterin therefore sees a way to introduce signature aggregation earlier.

The challenge lies in the size of the data. Eventually, sufficiently powerful quantum computers could compromise the elliptic curve cryptography that currently secures Ethereum accounts. A current signature occupies 65 bytes. According to Buterin, some resistant alternatives require 1,000 to 6,000. This represents 15 to more than 90 times more (according to our calculations). EIP-8288 retains 2 to 3 KB for hash-based signaturesreference for its cost calculations.

STARK proofs allow you to verify a calculation without having to reproduce it in full. Their size, however, exceeds 128 KB. It can reach 512 KB when rapid generation is favored, indicates the EIP-8288. Store so much data on Ethereum would therefore increase pressure on limited block space and transaction costs.

On Ethereum, the EIP-8288 aggregates signatures and proofs before entering the blocks

L’EIP-8288 proposes toaggregate post-quantum signatures and STARK proofs in a single block recursive proof. The nodes thus check all the cryptographic dependencies declared by the transactions, without processing each large piece of data individually. Each transaction declares these dependencies in the form of short references:

  • schema type;
  • imprint of signed data;
  • verification key.

The wallet still generates the post-quantum signature. Nodes that receive it through the mempool (the transaction queue) combine it with others, then combine those batches.

Decryption: a block would ultimately only contain a recursive STARK proof certifying that all declared dependencies are valid. Ethereum would therefore keep the payment instructions and the means to verify this proof, without storing each signature.

Technology Nature and role Status in EIP-8288
leanPCS Approach defended by Vitalik Buterin, based on a polynomial commitment scheme. It would provide a verification tool common to different proof systems. Absent from the current text.
leanSPHINCS Hash-based signature scheme, resistant to quantum attacks. Only schema usable in the current specification.
leanSTARK More general path, which would accept any signature scheme or confidentiality protocol. Reserved identifier. The footprint calculation of its dependencies remains to be defined in the draft.

The costs, however, change in scale. EIP-8288 cipher at 2-3 KB and 150,000 to 200,000 gas the direct verification of a hash-based signature. Gas measures the computational cost of an operation on Ethereum.

The draft sets 3,000 gas for a leanSPHINCS signature, plus 30,000 gas quota for the recursive proof. This equates to approximately 33,000 gas per addiction according to our reading of the text. This amount nevertheless remains a reference cost: the verification of the proof is carried out off-chain by the builder (the block constructor), specifies the draft, the parameters of which can still evolve.

leanPCS remains missing from Ethereum EIP-8288 draft

In the current text, only leanSPHINCS can be used. leanSTARK is provided, but its identifier is reserved until its fingerprint mechanism is defined. leanPCS is not there. This is an orientation defended by Buterin, not a provision of the draft.

leanSTARK, the most general option, would first require that Ethereum developers agree on a programming language for user programs. A difficult decision to change afterwards, according to Buterin. leanPCS would therefore offer comparable flexibility earlier, but would require more data on Ethereum, says CoinDesk.

Created on June 3, 2026 by Buterin and Thomas Coratger, EIP-8288 requires theEIP-8141. The latter introduces transactions composed of several execution frames (“frames”). The latter also remains a draft and the reference implementation of EIP-8288 is indicated “TBD”. The announcement follows calls, reported by CoinDesk on November 12has Prioritize Quantum Defenses in 2027 Update. However, no deployment date has been set.

The priority given to quantum defenses therefore extends Vitalik Buterin’s “Lean Ethereum” roadmap. Support for leanPCS, on the other hand, marks a technical preference, not a timetable. It remains to be seen whether leanPCS will be integrated into EIP-8288, whether EIP-8141 on which this draft depends will progress and whether other developers will follow Vitalik Buterin. File to follow…

Maximize your Tremplin.io experience with our ‘Read to Earn’ program! For every article you read, earn points and access exclusive rewards. Sign up now and start earning benefits.

Similar Posts