Vitalik Buterin Backs leanPCS to Speed Up Quantum-Safe Ethereum - Bitcoin Foundation

Ethereum Co-Founder Vitalik Buterin Supports leanPCS for Quantum-Safe Ethereum

Ethereum co-founder Vitalik Buterin has expressed his backing for leanPCS, considering it a faster path to making Ethereum quantum-safe. This approach allows ETH wallets to adopt larger, quantum-resistant signatures by bundling verification into shared proofs, thus reducing the need for permanent chain storage of extra data.

Buterin's Shift in Perspective

Buterin's endorsement, published on November 16, 2026, marks a significant change in his view of leanPCS. He now sees its potential after initially considering it "total bull." The key lies in a proposed shared verification process that still allows proof-system developers flexibility in their design choices.

Standardizing a Smaller Checking Tool

Buterin advocates for standardizing a smaller mathematical checking tool, which could enable developers to introduce proof aggregation sooner. This approach is in contrast to a broader overhaul, which might require a new computing language for the network to verify.

Benefits and Implementation

If implemented, the proposal offers enhanced wallet security and lower transaction costs. Currently, a standard Ethereum signature takes up 65 bytes, while quantum-resistant alternatives can require up to 6,000 bytes. Standardizing a smaller checking tool could streamline the process.

The Proposal's Timing

Buterin's endorsement comes on the heels of researchers advocating for prioritizing quantum defenses over faster blocks in Ethereum's 2027 upgrade. This puts leanPCS in the midst of an ongoing debate about upgrade priorities.

How EIP-8288 Works

EIP-8288, a draft proposal, suggests combining signatures and proofs at the block level. Wallets create signatures, which are then verified along with other signatures and application proofs. This verification is aggregated, ultimately resulting in a single mathematical proof.

Developer Choices and Trade-offs

Proof-system developers would build around the shared checking tool, making their own decisions regarding its implementation. Buterin highlights the trade-off between a smaller, more flexible approach and the potential benefits of a broader, more comprehensive solution.

Leave a Reply