Vitalik Buterin said Ethereum could lose an important efficiency edge if the network drops Poseidon hash, with the biggest effects falling on hash-based signature aggregation and the fast generation of state proofs inside blocks. His point was simple: Poseidon has delivered noticeably faster proof generation than traditional hash options, and that speed difference matters at the protocol level.
Proof generation speed sits at the center of the debate
Buterin argued that adopting Poseidon produced considerable gains in proof generation. For Ethereum, where scaling and verification efficiency remain central engineering goals, that is not a marginal improvement. Signature aggregation depends on handling large volumes of hashing work efficiently, while state proofs inside blocks affect how quickly data can be verified and relayed across the network. Both use cases are highly sensitive to the performance of the underlying hash function.
He described a model in which block producers prepare state proofs locally at high speed, then send both blocks and proofs to high-capacity external providers. Under that setup, large computing infrastructure could start contributing to Ethereum within minutes without downloading the full network state. That also opens the door to more flexible backup options and shortens the time required for new participants to get involved. A technical choice at the hash layer, in other words, can shape how the network is operated.
Support for Poseidon research does not rule out BLAKE improvements
Buterin also called for continued and rigorous research into the cryptographic security of Poseidon. At the same time, he backed work on making alternative hash functions more efficient, naming BLAKE as an example. In a statement on X, he said BLAKE is a strong and effective option, but losing the efficiency advantage offered by Poseidon would be a real setback, especially in signature aggregation and rapid state-proof production, where that edge could be decisive.
That position leaves room for multiple paths. Rather than tying Ethereum to one permanent choice, he argued for narrowing current performance gaps across different hash designs. If that happens, developers would have more freedom in later protocol changes and infrastructure decisions without giving up too much on speed or security.
Hash-function debate connects with wider architecture changes
The discussion also touched a broader question inside the Ethereum community. One member pointed to the ongoing initiative exploring a shift from the EVM to a RISC-V-based design, describing it as more than a technical upgrade and closer to a philosophical simplification of Ethereum’s verification layer. In that view, the transition could create unexpected challenges for crypto and AI teams by 2026, especially around the cost of generating cryptographic proofs.
Buterin also referenced the Ethereum Foundation’s “Strawman” roadmap, which projects shorter block creation and finalization times as more upgrades are introduced. Those targets sit within Ethereum’s long-term technical direction. The current argument over Poseidon, BLAKE, EVM, and RISC-V is really about the same trade-off: how Ethereum should balance efficiency, security, and flexibility in the design of its core architecture.