0x213cd93f213c…213cd93c
Buterin backs Ethereum plan for cheaper quantum-safe signatures
EIP-8288 would use recursive STARK aggregation to cut post-quantum verification costs, while Vitalik Buterin publicly reversed his skepticism of leanPCS.

Outputs
EIP-8288 was created June 3, 2026 and remains a draft with an unfinished reference implementation.
Ethereum’s standard signature is 65 bytes; post-quantum alternatives cited in the proposal run 2 to 3+ kB.
Post-quantum verification costs 150,000-200,000 gas, versus EIP-8288’s low-tens-of-thousands target.
Quantum-safe private transactions can require approximately 10 million gas.
The proposal estimates 64-96-byte dependency claims and also targets zero-knowledge proof aggregation.
EIP-8288, a draft Ethereum proposal created June 3, 2026, targets post-quantum verification in the low tens of thousands of gas, versus 150,000-200,000 gas for current alternatives, according to research cited in the proposal.
Ethereum co-founder Vitalik Buterin has publicly backed leanPCS, the approach at the center of EIP-8288. “Over the past few weeks I’ve gone from thinking leanPCS is total bull to being a total bull,” he wrote in a post on X.
The draft belongs to the Lean Ethereum roadmap, which targets post-quantum security and is projected for completion around 2028-2029.
What size and gas problem does EIP-8288 solve?
Ethereum’s standard signature occupies 65 bytes and uses cryptography that a sufficiently powerful quantum computer could, in theory, eventually break. The post-quantum replacements cited in EIP-8288 run 2 to 3+ kilobytes, making them substantially heavier.
Verifying those replacements costs 150,000-200,000 gas on Ethereum. A quantum-safe private transaction can reach approximately 10 million gas, which the proposal says puts that class of transaction out of reach for most everyday use.
How does recursive STARK aggregation work?
The draft places recursive STARK aggregation in Ethereum’s mempool, the waiting area where transactions sit before block inclusion. A STARK is a cryptographic proof that demonstrates a computation was correct without requiring others to repeat the work.
“Recursive” means proofs can verify other proofs. Under EIP-8288, many heavy signatures would be checked off-chain and folded into one compact proof, leaving transactions with small dependency claims instead of full signatures.
The draft estimates those claims at approximately 64-96 bytes, roughly the same range as today’s 65-byte standard signature. The bulk of the cryptographic data would stay off-chain rather than consume space in every transaction.
The proposal also aims to use the same aggregation approach for zero-knowledge proofs. That extends the proposed use beyond quantum-safe signatures and gives the mechanism a broader role in Ethereum’s cryptographic roadmap.
Why did Buterin reverse his position?
His reversal matters because leanPCS was not an obvious winner, even to him; the source describes a move from dismissive to enthusiastic over several weeks. Buterin’s public support gives the draft a prominent advocate, but it does not answer the remaining implementation questions.
The proposal’s technical premise is that cryptographic size and verification cost cannot keep rising without making post-quantum security impractical. Recursive aggregation attempts to separate the expensive verification work from the limited data every transaction must carry.
What changes for users and client teams?
For users, the main benefit would be lower gas use. The proposal’s central economic claim is straightforward: post-quantum verification requiring 150,000-200,000 gas would be hard to justify, while verification in the low tens of thousands of gas would be materially easier to absorb.
Private transactions carry the largest potential change. If offloading cryptographic data can meaningfully reduce the roughly 10 million gas required for a quantum-safe private transaction, the approach could make quantum-safe privacy practical rather than largely theoretical.
For client teams, the proposal moves much of the cryptographic checking off-chain but still requires on-chain dependency claims and an agreed implementation. EIP-8288 remains a draft with an unfinished reference implementation, not a shipped Ethereum feature.
Developers will need to assess the reference implementation, respond to feedback from client teams and determine whether the draft advances beyond draft status. The Lean Ethereum roadmap’s projected 2028-2029 completion window gives the work a broader schedule, but it does not turn EIP-8288’s gas and size estimates into deployed results.
Until implementation and client review advance, the low-tens-of-thousands gas target and 64-96-byte dependency claims remain proposal benchmarks rather than network measurements.
via Crypto Briefing (Source)
More from Daniel Okafor
Show full bio
Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.
1,514 articles