Key facts
- Buterin said leanPCS could be implemented quickly because far fewer design choices are needed than for leanSTARK.
- EIP-8288 would aggregate signatures and proofs into a single STARK before they reach a block, keeping most data offchain.
- Buterin said quantum-safe signatures would grow from 65 bytes to between 1 and 6 kilobytes, and proofs to around 128 kilobytes.
- leanSTARK would be fully general but would require Ethereum to agree on a new programming language, which Buterin said is likely to take time.
- A June Ethereum Research post shows a quantum-safe signature can be verified for about 150,000 gas without a protocol change, versus about 3,000 gas for ECDSA.
Ethereum co-founder Vitalik Buterin said on Monday, November 16, 2026, that he now supports leanPCS, one of three proposed ways to aggregate bulky quantum-safe signatures and proofs on Ethereum. In a lengthy explainer posted on X, he wrote: "Over the past few weeks I've gone from thinking leanPCS is total bull to being a total bull."
Buterin said quantum-safe signatures would grow from 65 bytes to between 1 and 6 kilobytes, while zero-knowledge proofs would grow from a few hundred bytes to around 128 kilobytes. "This is unsustainable to put on chain," he wrote. His answer is EIP-8288, a draft proposal he co-authored with developer Thomas Coratger in June, which would aggregate signatures and proofs before they reach a block. Under the design, users publish signatures or proofs, and network nodes repeatedly bundle what they have seen into a single STARK, a type of zero-knowledge proof, that attests the underlying data is valid. These aggregate proofs are combined until a single "master proof" verifies everything in a block, and only short claims rather than the full data would be stored onchain.
Buterin laid out three ways to build it. The simplest, leanSPHINCS, would support a single type of quantum-safe, hash-based signature at a small gas cost per signature but could do nothing else. At the other end, leanSTARK would be fully general, allowing any signature scheme, privacy protocols or hidden multisig logic, but Ethereum would first have to agree on a programming language for users' programs, which Buterin called "the first big case of 'Ethereum moving beyond the EVM'" and which is likely to take time.
