Vitalik Buterin proposes a new way to handle Ethereum cryptography
Oct 19, 2026
Ethereum co-founder Vitalik Buterin has backed EIP-8288 as a proposed way to support complex cryptography without repeatedly adding new verification functions to Ethereum, arguing that most heavy cryptographic work should happen outside the network’s main execution process.
In a series of October 19 posts on X, Buterin argued that Ethereum’s existing virtual machine and specialized cryptographic functions are unsuitable for supporting every new signature or proof system. He instead favored a design that would let users generate proofs locally and submit them through an aggregation mechanism.
The proposal, EIP-8288, would allow Ethereum to verify that cryptographic operations were performed correctly without including every original signature or proof in a block.
Vitalik Buterin described this approach as part of his vision for Ethereum as a cryptographic world computer, where substantial computation can happen outside the blockchain while its results remain verifiable.
Vitalik Buterin wants less cryptographic work inside Ethereum
Vitalik Buterin’s latest comments focus on how Ethereum handles cryptographic operations that require large amounts of computation or data.
Currently, developers can use the Ethereum Virtual Machine, or EVM, to run smart contracts that verify certain cryptographic statements.
EIP-8288 would combine proofs before they reach Ethereum
The proposed mechanism is described in EIP-8288, titled In-mempool signature and proof aggregation.
Buterin and Ethereum researcher Thomas Coratger created the proposal on June 3, 2026.
According to the official specification, the system would let transactions declare which cryptographic statements must be verified without including all of the original proof material in the final block.
Quantum-resistant signatures are a major part of the proposal
EIP-8288 includes support for cryptographic signatures designed to resist attacks from future quantum computers.
Ethereum currently relies on established digital signature systems for account authentication and blockchain consensus.
According to EIP-8288, hash-based signatures under consideration can require roughly 2–3 kilobytes and an estimated 150,000–200,000 gas to verify directly.
Recursive aggregation would start before block production
The proposed process does not depend solely on a block producer collecting every signature and generating one final proof.
EIP-8288 describes recursive aggregation beginning in Ethereum’s mempool, where transactions wait before being included in blocks.
Under the design, users would submit transactions along with the cryptographic evidence required to authorize them.
Mempool participants could validate the submitted evidence, combine several proofs into one and pass the resulting package to other participants.
EIP-8288 remains a draft requiring network approval
The official Ethereum Improvement Proposal repository classifies EIP-8288 as a draft standards-track proposal in the core category.
Its implementation would alter Ethereum’s consensus rules because blocks containing the proposed recursive proof format would not be understood by nodes running software without the update.
The specification identifies EIP-2718 and EIP-8141 as dependencies. Several implementation details remain incomplete, including parameters associated with the aggregated verification key and dependency hashing.
View sources >> Vitalik Buterin proposes a new way to handle Ethereum cryptography