Vitalik Buterin Backs leanPCS as Faster Route to Quantum-Safe Ethereum Under Draft EIP-8288
Vitalik Buterin says he has turned strongly in favour of leanPCS, an option in his draft EIP-8288 that would aggregate bulky quantum-resistant signatures and STARK proofs in the mempool instead of storing them on chain. The proposal has no reference implementation, no assigned upgrade and no launch date.

Table of Contents
Ethereum co-founder Vitalik Buterin said on November 16, 2026, that he has turned strongly in favour of "leanPCS", an option inside his draft proposal EIP-8288 that would let Ethereum absorb much larger quantum-resistant signatures and proofs without putting them on chain. The proposal is still a draft with no reference implementation, no assigned upgrade and no launch date.
In a long post on X published at 07:42 UTC on November 16 (11:12 Tehran time), Buterin wrote: "Over the past few weeks I've gone from thinking leanPCS is total bull to being a total bull." He then explained what the technique does, why he now prefers it as a first step, and why he believes it could bring what he called "the cryptographic proof singularity" to Ethereum "much faster than any of us expected".
This article explains what EIP-8288 proposes, what the three "lean" options mean, what is confirmed and what is not, and why the debate matters for ETH holders, wallet users and traders.
What Buterin said
Buterin's core argument is about data. According to his post, once Ethereum moves to quantum-safe cryptography, "signatures get bigger (65 bytes ECDSA -> 1-6 kB WOTS/SPHINCS depending on params) and ZKPs get much bigger (200-1000 bytes with groth16, PLONK, etc -> 128 kB with STARKs)." He added: "This is unsustainable to put on chain, and 8288 fixes this."
He described EIP-8288 as being about "hyper-scaling data and execution for any computation that needs to get performed on a piece of data once, the chain learns the answer, and then we never need to see that data again." That category, he wrote, covers most of the "heavy" work on Ethereum, including signatures, STARK proofs, Merkle branches and fully homomorphic encryption (FHE) computation, with signatures and STARKs being the most important.
CoinDesk reported the post at 3:18 a.m. EST on November 16 (11:48 Tehran time), and PANews published a separate summary the same day. Both reports match the content of the original post.
What EIP-8288 actually proposes
The official specification, titled "EIP-8288: In-mempool signature and proof aggregation", lists Vitalik Buterin and Thomas Coratger as authors and a creation date of June 3, 2026. It builds on EIP-8141, the "Frame Transaction" proposal, which restructures how Ethereum transactions handle validation, execution and gas payment.
According to the document's abstract, EIP-8288 adds a new frame mode in which transactions carry lightweight "dependencies", described as (scheme, data_hash, verification_key_hash) triples. These are "aggregated off-chain into a single recursive STARK", and a block is only valid if it includes that recursive STARK.
The motivation section is blunt about the cost problem. It says current hash-based signature proposals are "in the range of ~2-3 kB and ~150,000 to 200,000 gas to verify", and that hash-based zero-knowledge proofs "all take over 128 kB, or as much as 512 kB". Without aggregation, it says, privacy protocols would have "an impractically high cost".
How the aggregation would work
Buterin's post walks through the flow in plain steps:
A user creates a quantum-safe signature, a STARK proof or a polynomial-commitment opening and broadcasts it.
Network nodes listen. On each "tick", each node bundles the new objects it has seen into one STARK proving a list of claims, such as "pubkey P has signed message M".
Only hashes of inputs and outputs (about 64 to 96 bytes per claim, per Buterin) and one proof per tick are re-broadcast.
These proofs are aggregated again and again until a single "master proof" goes into the block.
The specification sets an AGGREGATION_INTERVAL of 1,000 milliseconds and says the STARK-related overhead for the block builder is "a fixed ~256 kB per AGGREGATION_INTERVAL milliseconds". It also limits each transaction to 16 leanSPHINCS signature dependencies and one leanSTARK dependency.
leanSPHINCS, leanSTARK and leanPCS explained
Buterin framed the choice as a question of "what is the underlying object that the user is creating?"
leanSPHINCS: one quantum-safe signature type
leanSPHINCS is a purely hash-based signature scheme. Buterin wrote that adding it would let users create quantum-safe accounts and pay "only a little bit of gas (4096 for the 64 bytes)" per signature. The draft specification currently lists a LEANSPHINCS_VERIFICATION_GAS constant of 3,000. The downside, in his words: "it's only one specific signature scheme, you can't do anything else."
leanSTARK: fully general, but slow to agree on
With leanSTARK, users could publish a STARK proof of any computation. Buterin listed possible uses including any signature scheme (lattice-based ones too), multisigs that hide their internal logic, privacy protocols and "private account abstraction". The catch is that Ethereum would need to fix the instruction set architecture (ISA) for those programs. He called that "a really big deal", "the first big case of 'Ethereum moving beyond the EVM'", likely to take time and hard to upgrade later.
leanPCS: the shortcut Buterin now favours
PCS stands for polynomial commitment scheme, a cryptographic proof that a committed polynomial takes a certain value at a given point. Buterin described PCSes as "by far the most important 'hard' component of a STARK". With what he called a "magic PCS oracle", a STARK could be verified in "~20-40k gas", he wrote.
Specifying a PCS mainly requires choosing a mathematical field, and he pointed to the 128-bit binary field as a natural option. He acknowledged that leanPCS is "less efficient than leanSTARK onchain" but said it gives "the same generality as leanSTARK, in a way that could potentially be implemented very quickly", with leanSTARK addable later once the ISA is settled.
What is confirmed and what is not
Item | Status |
|---|---|
Buterin publicly backs the 8288 + leanPCS route | Confirmed (X post, Nov 16) |
EIP-8288 exists with a published specification | Confirmed (eips.ethereum.org) |
Reference implementation | Listed as "TBD" in the specification |
Key constants such as AGGREGATED_VK | Still "TBD" |
leanPCS details in the official text | Not yet; the current text defines leanSPHINCS and leanSTARK schemes |
Inclusion in a named upgrade or a launch date | Not announced |
This is the key point for readers: a strong endorsement from Ethereum's best-known researcher is not a decision by core developers. Ethereum upgrades are agreed on public All Core Developers calls, and no such decision on EIP-8288 has been reported.
Why this matters now
The post lands in a week when quantum security has moved up Ethereum's agenda. On the ACDC #191 call on November 12, developers withdrew the Quick Slots plan from the Hegotá upgrade and advanced EIP-8483 for early post-quantum key registration by validators, as we reported here. Other networks are working on similar problems; the XRP Ledger, for example, has outlined quantum-resistant accounts on a 2028 roadmap.
EIP-8483 deals with the consensus layer, the validators. EIP-8288 targets the execution layer, the transactions that ordinary users sign. If wallets eventually switch to quantum-safe signatures, data size becomes a direct cost issue for users, because larger transactions consume more block space and can push up fees.
What it means for users and the market
For wallet users: nothing changes today. Existing ECDSA accounts work as before, and no action is required. Be wary of anyone offering a "quantum-safe ETH migration" or asking for seed phrases in connection with this news; there is no such official process.
For developers: the proposal signals where Ethereum's long-term design is heading, toward proof aggregation in the mempool and less reliance on putting raw cryptographic data on chain. Privacy tools and account-abstraction wallets could be among the biggest beneficiaries if the design ships.
For traders: this is a long-dated technical story, not a near-term catalyst. ETH has been under heavy pressure this month; for the market context see our latest ether analysis. Research endorsements rarely move fundamentals until code, testnets and a fork schedule exist.
Risks and open questions
The specification itself lists the trust assumptions. Security depends on the soundness of the Lean Ethereum circuits, the hash function used for dependency hashes (BLAKE2s in current tooling, with BLAKE3 "the leading choice to replace it") and recursive STARKs. It says recursion soundness "is widely believed to be true" but adds "difficulty to end-to-end formally proving the scheme".
There are also design costs. The document notes that a recursive STARK in each block header "does increase the block header size greatly". It also raises denial-of-service risks from transactions with many dependencies, which is why it caps signatures and STARKs per transaction. Builders and mempool nodes would take on new proving work.
Timeline
Jan 29, 2026: EIP-8141 (Frame Transaction) created.
Jun 3, 2026: EIP-8288 created by Buterin and Coratger.
Nov 12, 2026: ACDC #191 withdraws Quick Slots from Hegotá and advances EIP-8483.
Nov 16, 2026, 07:42 UTC (11:12 Tehran): Buterin publishes his leanPCS post.
Nov 16, 2026, 08:18 UTC (11:48 Tehran): CoinDesk reports the post.
Key terms
Quantum-safe (post-quantum) signature: a signature scheme believed to resist attacks by large quantum computers.
STARK: a type of zero-knowledge proof that relies on hash functions and is considered quantum-resistant.
Mempool: the pool of pending transactions before they are included in a block.
Recursive proof: a proof that verifies other proofs, letting many be compressed into one.
ISA: instruction set architecture, the "language" programs must be written in.
What to watch
Whether the EIP-8288 text is updated to define a leanPCS scheme.
Discussion on the Ethereum Magicians thread and on All Core Developers calls.
A reference implementation and test results from the Lean Ethereum tooling.
Whether client teams propose EIP-8288 for Hegotá or a later fork.
FAQ
Has Ethereum adopted EIP-8288?
No. It is a draft proposal. No upgrade inclusion or launch date has been announced.
Do I need to move my ETH because of quantum risk?
No official migration exists. Treat any such request as a likely scam.
What did Buterin change his mind about?
He now favours leanPCS as a faster first step that keeps general-purpose flexibility, instead of waiting for agreement on a full leanSTARK instruction set.
Sources
Vitalik Buterin, post on X, Nov 16, 2026, 07:42 UTC
EIP-8288: In-mempool signature and proof aggregation, created Jun 3, 2026
CoinDesk, Nov 16, 2026, 3:18 a.m. EST
PANews, Nov 16, 2026
This article is for information only and is not investment advice.
- ETHEthereum
See the signals and their results
Browse publicly logged signals and how they performed, or create a free account to follow them.





