The Ethereum Foundation is reportedly reconsidering its approach to cryptographic hashing within the network’s proof infrastructure. According to a report from CryptoBriefing, the organization is moving away from Poseidon, a hash function widely used in zero-knowledge proof systems, and toward SHA and BLAKE, two families of hash functions with longer track records in mainstream cryptography.
Poseidon was designed specifically to be efficient inside zero-knowledge circuits. Its structure reduces the computational cost of generating cryptographic proofs, which made it attractive for Ethereum’s rollup and zk-EVM efforts. Many layer-2 networks and proof systems built on Ethereum have used Poseidon or similar algebraic hash functions for this reason.
SHA, short for Secure Hash Algorithm, and BLAKE are general-purpose cryptographic hash functions. Both have been studied extensively by cryptographers and are used across a wide range of security-critical systems, including Bitcoin and other blockchain networks. They are not optimized for zero-knowledge proving in the way Poseidon is, but they carry a longer history of independent scrutiny.
The reported shift, if accurate, would suggest the Ethereum Foundation is prioritizing proven security assumptions over proving efficiency in certain parts of its technology stack. Newer, purpose-built cryptographic primitives like Poseidon can offer performance advantages, but they typically have shorter histories of external review than algorithms like SHA-256 or SHA-3, which have been in use for years.
The report does not specify which components of Ethereum’s roadmap would be affected by the change, nor does it detail a timeline for implementation. It is also unclear whether the shift would apply broadly across the protocol or to a narrower set of applications, such as specific proof systems or client implementations.
Ethereum’s core development process typically involves extensive discussion among researchers, client teams, and the broader community before any cryptographic primitive is formally adopted or replaced. Changes to hash functions used in consensus-critical or proof-related components generally require careful auditing given the security implications involved.
This report has not yet been corroborated by other outlets, and additional details from the Ethereum Foundation itself have not been independently reviewed. Readers should treat the specifics of the reported change as preliminary until confirmed through official channels or additional reporting.
Sources disagree on this story
This article was published before the reports below were compared. The reporting above stands; what follows is where the published accounts do not agree.
CryptoBriefing and crypto.news agree the Ethereum Foundation is dropping Poseidon for standard hashes, but give different origin dates for Poseidon and different named replacement algorithms.
What all sources agree on
- The Ethereum Foundation, via researcher Justin Drake, is moving Ethereum's L1 roadmap away from Poseidon toward established hash functions.
- The shift is attributed to advances in binary-field SNARKs that let traditional hashes match Poseidon's performance in ZK proof systems.
- A production-grade leanVM is scheduled for 2027, with layer deployments (consensus, data, execution) in 2028.
- Poseidon was originally designed to be efficient inside zero-knowledge proof systems / SNARKs.
- Drake described the shift using the phrase 'hash-friendly SNARKs' rather than 'SNARK-friendly hashes.'
Where the reports disagree
1Origin year of the Poseidon hash function
The hash function itself dates back to 2021, co-designed by cryptographer Dmitry Khovratovich.
Poseidon emerged in 2019 as a hash function designed for zero-knowledge proof systems.
What would settle it: The original Poseidon academic paper's publication date.
2Which specific BLAKE variant the foundation is favoring
the foundation is now favoring SHA and BLAKE3, two well-established alternatives
pursue established hash functions such as SHA-2 or BLAKE2s
What would settle it: Justin Drake's original Aug. 13 X post naming the specific hash functions under consideration.
What to make of it
Treat the overall direction — Ethereum's L1 roadmap moving away from Poseidon toward standard hashes, with a 2027 leanVM and 2028 deployment target — as established across all four outlets; the exact origin year of Poseidon and the specific BLAKE variant named are unresolved until Drake's original post or an EF statement is checked directly.
Market Impact
Any change to Ethereum's underlying cryptographic tooling has implications for developers building rollups, zk-EVMs, and other proof-based applications on the network. A move toward SHA and BLAKE could affect the performance characteristics of zero-knowledge proof generation, since these functions are not natively optimized for zk-circuits the way Poseidon is.
For now, there is no indication that this reported shift has had a direct effect on ETH's price or broader market sentiment. The story is primarily relevant to developers and infrastructure teams working on Ethereum's scaling roadmap, rather than to short-term trading activity.
The reported move away from Poseidon toward SHA and BLAKE highlights an ongoing tension in blockchain cryptography between proving efficiency and long-tested security. Further confirmation from the Ethereum Foundation or additional reporting would help clarify the scope and timing of any such change.
Frequently Asked Questions
What is Poseidon hash and why does it matter for Ethereum?
Poseidon is a cryptographic hash function designed to be efficient inside zero-knowledge proof circuits. It has been used in various rollup and zk-EVM projects tied to Ethereum's scaling roadmap.
How are SHA and BLAKE different from Poseidon?
SHA and BLAKE are general-purpose cryptographic hash functions with long histories of independent security review. Poseidon was purpose-built for zero-knowledge proving efficiency, a newer and less broadly tested design goal.
Has the Ethereum Foundation officially confirmed this change?
As of this report, the shift has been described by CryptoBriefing but has not been independently confirmed through official Ethereum Foundation statements.
Would this change affect existing Ethereum applications immediately?
The report does not specify a timeline or list which components would be affected, so any practical impact on existing applications remains unclear at this stage.