0x461aecea461a…461aeced

ConfirmedSecurity827 vB86 sat/vB4 min decode

Vitalik Buterin Backs leanPCS for Quantum-Safe Ethereum

Vitalik Buterin backed leanPCS, a draft Ethereum design that aggregates quantum-resistant signatures and application proofs, reducing permanent storage needs ahead of 2027 upgrade planning.

Vitalik Buterin Backs leanPCS to Speed Up Quantum-Safe Ethereum
WitnessVitalik Buterin Backs leanPCS to Speed Up Quantum-Safe EthereumWorldSpectrum / pixabay

Outputs

  1. Vitalik Buterin backed leanPCS on November 16, 2026.

  2. Ethereum’s standard authorization signature is 65 bytes; some quantum-resistant alternatives require about 1,000–6,000 bytes.

  3. EIP-8288 remains a draft with an unfinished reference implementation ahead of the planned 2027 upgrade.

  4. A 1,000-byte alternative is about 15 times the standard size; 6,000 bytes is about 92 times.

  5. The 2027 upgrade debate pits quantum defenses against faster blocks.

Ethereum co-founder Vitalik Buterin backed leanPCS on November 16, 2026. Some quantum-resistant signature alternatives require about 1,000–6,000 bytes. The draft proposal aims to make them practical for wallets.

“Over the past few weeks I’ve gone from thinking leanPCS is total bull to being a total bull,” Buterin wrote on X, according to CoinDesk.

That reversal brought a prominent advocate to a narrower path. LeanPCS standardizes one small mathematical checking tool. Different proof systems would share it. Developers would keep choosing the rest of their architecture.

Ethereum’s standard authorization signature occupies 65 bytes, according to Buterin’s figures. That figure excludes the transaction’s other instructions. A 1,000-byte alternative is about 15 times larger. A 6,000-byte alternative is about 92 times larger.

Storing each signature separately would increase block-space demand. That could raise fees for token transfers and application use. EIP-8288 aims to avoid the burden.

The proposal treats proof aggregation as a way for developers to introduce stronger signatures sooner than a broader overhaul of Ethereum’s computing model would allow.

What changes for Ethereum wallet users?

Under EIP-8288, wallets would still sign payment authorizations. Those signatures could use quantum-resistant cryptography.

Computers receiving the signatures would combine their checks with other signatures. They would also combine application proofs. Repeated aggregation would collapse the batches into one mathematical proof.

That proof would travel in a block alongside payment instructions and enough data to check it. Ethereum could verify the combined result without permanently storing each signature.

LeanPCS addresses the common checking tool inside that workflow. Proof-system developers would build the surrounding architecture. They would decide how the remaining work runs.

For ETH wallet users, the practical change is conditional. Stronger authorization could arrive without storing every bulky signature onchain. If developers build the system as intended, storage-related fees could fall.

Privacy applications could use the same aggregation. Their mathematical proofs may also grow under stronger cryptography. Bundling them with wallet checks could reduce the proof data each user pays to store.

A shared result can stand in for separate checks, potentially lowering permanent storage costs while leaving the underlying signatures outside Ethereum’s long-term onchain record.

The trade-off inside EIP-8288

The trade-off is more information onchain. The broader alternative would require a new computing language. Ethereum developers would have to agree on it for programs the network verifies.

Buterin describes that commitment as substantial. Changing the language later would be difficult. LeanPCS limits agreement to the shared component. It may deliver similar flexibility sooner.

A wallet-signature aggregation system must exist first. EIP-8288 remains a draft. Its published specification lists the reference implementation as unfinished.

February 27 coverage from crypto.news described a phased quantum-resistance roadmap. It covered consensus, data availability, wallets and application proofs. The plan proposed hash-based or lattice-based cryptography. Recursive STARK aggregation would support those replacements.

The roadmap identified four vulnerable areas:

  • Consensus-layer BLS signatures.
  • Data availability using KZG commitments.
  • Wallet signatures using ECDSA.
  • Application proofs such as Groth16.

That roadmap also tied wallet migration to native account abstraction under EIP-8141. Wallets could adopt post-quantum schemes once efficient implementations arrived.

July coverage from CryptoBriefing placed quantum safety within Ethereum’s broader Lean Ethereum direction. It sat beside operational simplification and statelessness. The report cited a Strawmap of about seven anticipated hard forks. Those forks were expected from 2026 through 2030. LeanPCS narrows those ambitions to one engineering decision.

By standardizing only one mathematical component, leanPCS offers an earlier path through a consequential design choice, but accepts additional onchain data as the central trade-off.

The 2027 upgrade decision

The endorsement came days after researchers called for a priority choice. They wanted quantum defenses ahead of faster blocks in Ethereum’s planned 2027 upgrade. Security work now competes with an immediate user benefit.

Quantum computers powerful enough to break current cryptography could forge signatures. They could compromise wallets. Replacing vulnerable cryptography addresses one half of the problem. Making verification affordable addresses the other.

The unfinished reference implementation is the clearest next milestone. Progress on the verification framework will determine the design. The retained onchain data will determine its savings.

Three tasks come next. The reference implementation needs completion. A verification framework needs selection. Upgrade planners need to place quantum defenses within the 2027 plan. These choices will determine whether Ethereum standardizes more now or leaves more decisions to individual proof-system developers.

Without effective aggregation, stronger cryptography would still carry a storage penalty as wallets, application proofs and privacy systems handle bulky verification data on the chain.

Separately, a related Bitcoin Foundation report said two proposals aim to protect 200,000 contracts from the Glamsterdam upgrade.

The next checkpoints are the reference implementation, the chosen verification framework and quantum defenses’ place in the 2027 upgrade. Those decisions will determine whether stronger wallet protection arrives with manageable storage costs.

via bitcoinfoundation.org (Source)

More from Marcus Bennett

Marcus Bennett

Show full bio

Senior reporter covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.

1,456 articles