Ethereum’s long-term cryptography strategy has become the subject of renewed debate after Vitalik Buterin argued that the network should avoid adding extensive cryptographic functionality directly to its execution layer. Instead, the Ethereum co-founder advocates using EIP-8288 to verify complex computations through STARK proofs generated outside the blockchain.
The discussion highlights a growing challenge for Ethereum developers: preparing the network for future cryptographic threats while keeping transaction data manageable and preserving flexibility for developers.
Vitalik Buterin Makes the Case for EIP-8288
In a recent post, Buterin argued that Ethereum’s Ethereum Virtual Machine (EVM) and precompiles are not the ideal places to accommodate most additional cryptographic operations. Both approaches require data to be processed through the blockchain’s execution environment, potentially increasing the amount of information that must be included in blocks.
Buterin pointed to practical limits on blockchain data capacity, estimating that Ethereum could face discomfort at approximately 8 MB per second, even with PeerDAS and blocks-in-blobs. His argument is that adding more cryptographic operations directly to the main execution process could create unnecessary pressure on limited blockspace.
His proposed alternative centers on EIP-8288 and STARK proofs. Under this approach, users or applications would perform computationally intensive operations locally, generate a cryptographic proof that the work was completed correctly, and submit that proof for verification and aggregation.
The blockchain would verify the result without needing to process all the underlying data and computation. Buterin argues that this architecture could allow Ethereum to support a wider range of cryptographic systems while keeping the base layer comparatively lean.
This could matter as applications explore cryptographic techniques designed to withstand future quantum-computing threats. Rather than requiring Ethereum to introduce a dedicated precompile for every new signature scheme, developers could potentially use locally supported cryptography and prove its validity through the proposed mechanism.
Buterin also suggested that client-side proof generation is becoming faster, including on mobile devices. However, the practical benefits will depend on implementation, proving costs, verification requirements, and how efficiently the proposed aggregation system operates.
Lattice Cryptography and AI Security Raise Questions
The discussion also reflects disagreement over the readiness of post-quantum cryptographic systems. Starknet founder Eli Ben-Sasson challenged the idea that lattice-based cryptography should be trusted for high-value applications without more time for testing.
Ben-Sasson argued that lattices possess mathematical structures that could make them attractive targets for AI-assisted attacks. He also questioned the maturity of succinct cryptographic systems based on module Short Integer Solution (module-SIS), noting that these approaches have existed since around 2012. He recommended allowing another three to five years of scrutiny before entrusting substantial value to them.
Gabriel Shapiro, known as @lex_node, offered a different perspective after reconsidering Ethereum’s roadmap amid recent concerns raised by venture capital firm Andreessen Horowitz (a16z) and Ethereum researcher Justin Drake. Shapiro said his investigation left him believing Ethereum’s approach remained the best option for the network, while acknowledging his limitations as a non-mathematician.
Buterin has also indicated that lattice-based cryptography could eventually support accounts and wallets through a precompile if the relevant systems are demonstrated to be secure against AI-assisted attacks. His latest argument, however, emphasizes a broader architectural solution rather than relying on additional precompiles.
For Ethereum users, the distinction is important. Supporting new cryptographic methods is not simply a matter of adding code; developers must also consider security assumptions, computational costs, data availability, and the consequences of potential failures.
EIP-8288’s proposed role in this debate is to separate cryptographic computation from the blockchain’s main execution process. Whether it becomes the preferred path will depend on technical implementation, security reviews, and developer adoption. The exchange does not establish that lattice cryptography has been broken by AI, nor does it confirm that the proposed architecture is already deployed. Instead, it exposes a central question for Ethereum’s future: how to expand cryptographic flexibility without making the network harder to scale or secure.
About The Author
