
Vitalik Buterin Backs leanPCS as Path to Quantum-Safe Ethereum Signatures
Ethereum co-founder Vitalik Buterin publicly endorsed leanPCS and the draft EIP-8288 after initially dismissing the approach, citing sharply lower on-chain costs for post-quantum signatures. The proposal remains an unfinished draft with no shipped reference implementation.
Written by CoinArticle’s AI Newsroom · from 2 cited sources. How we work
Buterin Reverses Position on leanPCS
Ethereum co-founder Vitalik Buterin said on X that he had moved from viewing leanPCS as "total bull" to being a "total bull" on it, after several weeks of comparing approaches. He is a co-author of EIP-8288, a draft written with Thomas Coratger and dated June 3, 2026, that sits within the broader Lean Ethereum roadmap targeting post-quantum security.
The reversal is notable because Buterin's own account describes leanPCS as not an obvious choice even for its strongest proponents. His support is for the EIP-8288 framework that leanPCS would serve, rather than a finished feature.
The Size and Gas Problem
The underlying issue is data size. A standard Ethereum signature today is 65 bytes, but the post-quantum replacements are much heavier. Buterin put post-quantum signatures at 1 to 6 kilobytes under the scheme he discussed, and STARK proofs at up to 128 kilobytes. Research findings on the proposal put current post-quantum signatures at 2 to 3-plus kilobytes, with on-chain verification costing 150,000 to 200,000 gas.
The two sources differ on the scale of these figures, and the gap is not reconciled in the reporting. Quantum-safe private transactions are the most expensive case, with costs reportedly reaching roughly 10 million gas, which would put them out of reach for most everyday use.
How EIP-8288 Would Work
EIP-8288 proposes aggregating signatures and STARK proofs inside Ethereum's mempool, the queue where pending transactions wait before inclusion in a block. Nodes would check the heavy evidence off-chain and produce a STARK confirming specific claims, such as that a key signed a message. Those proofs can be recursively combined until a block builder produces a single proof covering the relevant transactions.
On-chain, Ethereum would keep only short dependency claims. Buterin estimated these at roughly 64 to 96 bytes per claim, close to today's 65-byte signature. One source describes the earlier version as using 96-byte dependency entries and one block-level recursive STARK that validators must check. The proposal aims to bring post-quantum verification costs down to the low tens of thousands of gas, compared with the current 150,000 to 200,000 range. Those projected figures are design targets, not measured results.
The Three Approaches Compared
Buterin weighed three options. LeanSPHINCS would aggregate hash-based signatures for quantum-resistant wallets and multisignature accounts. A separate SPHINCS-minus research proposal describes Ethereum-compatible hash-based signatures that avoid introducing a new cryptographic primitive. LeanSTARK offers the most generality, letting users prove almost any computation, which opens privacy and custom authorization designs.
LeanSTARK would require Ethereum developers to first agree on an instruction-set architecture for expressing those computations, which Buterin called "the first big case of 'Ethereum moving beyond the EVM'." LeanPCS, where PCS stands for polynomial commitment scheme, sidesteps that decision for now. Buterin said a PCS verification feature could let developers check complex STARK proofs through existing execution at around 20,000 to 40,000 gas, and argued it could offer leanSTARK's generality "in a way that could potentially be implemented very quickly."
Status and What to Watch
EIP-8288 is a draft. The reference implementation is unfinished, and no client team has committed to shipping it in the reporting reviewed. Next steps to track are progress on the reference implementation, feedback from Ethereum client teams, and whether the EIP advances beyond draft status.
Why It Matters
For Traders
Near-term price impact is unlikely since EIP-8288 is an unfinished draft, so watch for implementation milestones rather than the endorsement itself.
For Investors
Quantum-safe signature costs are a long-horizon constraint on Ethereum's security model, and a credible path to low gas overhead would reduce a major adoption risk.
For Builders
Developers building signature or account abstraction logic should track leanPCS and EIP-8288, since the choice between leanSPHINCS, leanSTARK and leanPCS changes the verification interface they will target.
This article is for information only and is not financial advice. Read the full disclaimer.





