From the Blackmint News archive. Prices and details may have changed since publication.
Buterin Backs leanPCS as Faster Route to Quantum-Safe Ethereum
Quantum-safe signatures can run 1 to 6 kilobytes against 65 bytes today. EIP-8288 would fold them into one proof per block, but it is still a draft.
Vitalik Buterin said early Monday that he now backs a "leanPCS" version of EIP-8288, a draft Ethereum proposal meant to stop quantum-safe signatures, up to about 6 kilobytes each, from crowding blocks. Today's signatures take 65 bytes.
"Over the past few weeks I've gone from thinking leanPCS is total bull to being a total bull," the Ethereum co-founder wrote on X at 2:42 a.m. ET.
Bigger data takes more of Ethereum's limited block space, which can push fees up. Signatures and proofs built to resist quantum computers are much bigger. The EIP text puts hash-based signatures at about 2 to 3 kB and 150,000 to 200,000 gas to verify, and STARK proofs at over 128 kB.
How the bundling works
A user still creates the large signature or proof and broadcasts it. Nodes holding pending transactions (the mempool) check what they have seen and, once per second under the draft, roll it into a single STARK, a hash-based proof that a list of checks passed. Those proofs get merged again until a block carries one "recursive STARK" in its header. The chain then stores short claims, about 64 to 96 bytes each by Buterin's count, instead of every signature.
Three options on the table
leanSPHINCS covers one hash-based signature type and nothing else. leanSTARK lets users prove any program, but developers would first have to agree on the instruction set those programs use; Buterin called that "a really big deal" because it would be hard to upgrade. leanPCS standardizes only a polynomial commitment scheme, the hardest part of a STARK. Buterin wrote that it could be built "very quickly" and that leanSTARK could follow later, though leanPCS is less efficient onchain.
Draft only, no date
The EIP, by Buterin and Thomas Coratger, was created June 3. Its reference implementation is listed as "TBD," and it would need a network upgrade. The published spec defines leanSPHINCS and leanSTARK modes. It does not yet describe a leanPCS mode.
Sources: Vitalik Buterin on X (Nov. 16, 2026) · EIP-8288: In-mempool signature and proof aggregation (draft) · Ethereum Magicians: EIP-8288 discussion · CoinDesk: Vitalik Buterin backs a faster route to quantum-safe Ethereum
Revisions
First published .
No revisions since publication.
We fix errors and say so. See every correction on the Blackmint corrections page.