Ethereum researcher Justin Drake mentioned on Aug. 13 that the Ethereum Basis is abandoning Poseidon for future layer-1 (L1) designs and pivoting towards SHA or BLAKE hashes after eight years of labor on specialised, proof-friendly cryptography.
Drake reported no break in Poseidon and issued no migration order, noting that latest features in proof programs modified the efficiency tradeoff that had favored the hash.
SNARKs produce compact proofs {that a} computation was carried out appropriately. Many use arithmetic over giant prime fields, the place the bitwise operations behind typical hashes reminiscent of SHA-256 and Keccak traditionally imposed a excessive proving value. Poseidon was designed to decrease that value by becoming the proof system’s most popular math.
Binary-field proofs increase hash throughput
Binius analysis binary-field development works naturally with 0s and 1s, intently matching Keccak’s bitwise operations. The Flock paper, posted July 29, applies newer methods to giant batches of ordinary hash computations.
Flock’s authors report that one M4 Max core can show about 82,000 BLAKE3 compression evaluations, 42,000 SHA-256 compressions, and 30,000 Keccak permutations per second. Ten cores exceeded 660,000 BLAKE3 compressions per second, and SHA-256 proving ran greater than 9 instances sooner than Binius64 within the paper’s comparability.
The proof-of-concept benchmark counts inner hash operations, whereas Ethereum transaction capability and manufacturing throughput use totally different measurements.
Drake described the advance as a reversal in cryptographic design: researchers have constructed hash-friendly SNARKs, decreasing the necessity for SNARK-friendly hashes. Typical hashes can enter Ethereum’s design course of with out carrying their former proving penalty.
SHA-256 is a part of NIST’s Safe Hash Commonplace. BLAKE2 has had a public informational specification since 2015, separating it from the newer BLAKE3 implementation benchmarked by Flock.
Years of public evaluation give cryptanalysts extra time to check its design, and sooner proofs now let Ethereum weigh that historical past with out selecting a youthful primitive primarily for proving pace.
Ethereum’s safety roadmap individually identifies protocol simplification as a solution to shrink the community’s assault floor.
Ethereum plans to interchange validator BLS signatures with hash-based leanXMSS signatures, then use leanVM to combination their a lot bigger information into compact proofs. Low-cost proofs of typical hashes would take away one impediment from that structure.
Drake’s private strawmap locations production-grade leanVM round 2027 and deployments throughout the consensus, information and execution layers in 2028. Ethereum’s official post-quantum roadmap provides a nonbinding goal of about 2029 for core infrastructure and extends full execution-layer migration past that time.
Ethereum’s roadmap tells customers to go away their wallets unchanged for now, whereas Drake’s announcement requires no adjustments to current rollups or zkVMs and describes no deployed fork. The choice issues which hash foundations Ethereum might use in a future proof-driven L1.
