The Ethereum Foundation has decided to move away from the Poseidon hash function in its plans for a future base-layer design, with the shift confirmed by core researcher Justin Drake on August 13, 2026.
ETH
SOL
BSC
ROBINHOOD
USDT
AAPLAdvances in Binary-Field Proof Systems Change Calculus
Justin Drake explained that recent breakthroughs in proof systems operating over binary fields have changed the balance between traditional hash functions, such as SHA-2 and BLAKE, and specialized SNARK-friendly hashes like Poseidon. These improvements now allow standard hash functions to achieve performance comparable to Poseidon within zero-knowledge SNARK proofs.
Poseidon, launched in 2019, was especially designed to be efficient inside SNARK (Succinct Non-interactive ARguments of Knowledge) proofs and rapidly became Ethereum’s default SNARK-friendly hash. However, advances led by Binius research, notably from Benjamin Diamond and Jim Posen, as well as the more recent Flock development, have contributed to these new efficiencies in binary-field SNARKs.
Drake estimated that new systems such as Binius and Flock can process roughly 1 million conventional hash computations per second on a standard laptop, with a speed around 100 times slower than native CPU hashing but still practical for SNARK purposes.
Mini dictionary: Poseidon is a cryptographic hash function optimized for zero-knowledge proof systems like SNARKs, offering efficient computation within those contexts. In contrast, SHA-2 and BLAKE are widely adopted standard hash functions considered secure under established cryptographic assumptions.
Drake pointed to research efforts such as Binius and Flock for creating new possibilities, saying they have shifted the trade-off between specialized and traditional hash functions for SNARKs. The result is that “newer binary-field proof systems can efficiently handle the kinds of operations that established hash functions perform.”
In effect, the proposed update would make established hashes such as SHA-2 and BLAKE more viable for Ethereum’s future cryptographic foundations, lessening the need for a specialized function like Poseidon in new base-layer designs.
Connection to Ethereum’s Post-Quantum Strategy
Drake linked the hash function decision to Ethereum’s broader post-quantum security strategy. He argued that the project should continue to rely on well-established cryptographic principles and adopt a cautious stance regarding novel approaches. He drew attention to previous difficulties with innovative schemes such as HAWK, a lattice-based signature protocol, and SQIsign, which is based on isogeny theory, both of which have faced recent setbacks.
This conservative approach forms part of Ethereum’s long-term plans to keep its cryptographic systems resilient in the era of quantum computation. Ensuring that cryptographic assumptions remain strong is a key focus as the network prepares for potential quantum threats in the future.
The move signals a commitment to established cryptographic methods, aligning Ethereum’s roadmap with its post-quantum ambitions and lessons learned from past protocol challenges.
Transition Timeline and Developer Impact
Drake clarified that the proposed change will not render Poseidon obsolete for current applications. There is no immediate requirement for existing developers to migrate, as the shift pertains only to upcoming base-layer designs.
The Ethereum Foundation targets 2027 for the launch of a production-grade leanVM, with targeted rollouts for consensus, data, and execution layers expected in 2028. The intention is to gradually transition toward a more robust and conventional cryptographic basis for the protocol’s next evolution.
| Milestone | Target Date |
|---|---|
| leanVM production release | 2027 |
| Consensus layer rollout | 2028 |
| Data & execution layers rollout | 2028 |
This planned architectural adjustment reflects Ethereum’s intent to update its foundational security while leveraging improved proof systems, ensuring long-term resilience without disrupting existing projects.
