Digital Currency

Add as a preferred source on Google

Ethereum's EIP-8288 Draft Omits leanPCS From Signature Plan

The draft specifies leanSPHINCS, reserves leanSTARK for future use, omits leanPCS and lists its reference implementation as “TBD.”

Updated 2 min read
Developers sketch a proof-verification diagram during a technical meeting in Zug, Switzerland / TokenPost.ai (mono)
Developers sketch a proof-verification diagram during a technical meeting in Zug, Switzerland / TokenPost.ai (mono)

Ethereum's EIP-8288 draft omits leanPCS, leaving out a proof-checking approach that could help manage the larger data load expected from post-quantum signatures on the network.

The EIP-8288 draft proposes that nodes combine signature checks from multiple transactions in Ethereum’s mempool, then produce a recursive STARK for each block to show the checks succeeded. A recursive STARK incorporates other proofs. The design would keep transaction instructions and proof-verification information available, while allowing individual signatures to be discarded instead of stored permanently.

The EIP-8288 draft, created June 3, 2026, names the hash-based leanSPHINCS scheme and reserves leanSTARK for future use. The draft omits leanPCS and lists its reference implementation as “TBD.”

Ethereum account signatures use elliptic-curve cryptography and measure 65 bytes. In his post, Buterin estimated post-quantum alternatives at 1,000 to 6,000 bytes per signature. He put hash-based signature verification at 150,000 to 200,000 gas per signature. Buterin also estimated a STARK proof at about 128 kilobytes, or up to 512 kilobytes when generated quickly, with verification using millions of gas. These figures are estimates, not test results.

In a post, Ethereum co-founder Vitalik Buterin backed leanPCS as a way to manage the added data burden. The method would establish shared procedures for checking proofs while leaving other technical choices open. One trade-off is that Ethereum would retain more verification information on-chain than under a design based on a network-wide computation language. The proposal addresses verification overhead; it would not replace Ethereum’s existing cryptography by itself.

In privacy applications, aggregating proofs could distribute their data costs among several transactions. Zero-knowledge proofs can show that a transaction meets conditions without disclosing its details.

The EIP-8288 draft remains a proposal, and Buterin’s post gives no upgrade schedule.

Related articles

View all