The Ethereum developer community has wrapped up its analysis of Fusaka Devnet 2 with mixed results: just 56 percent of clients reached finalization, exposing critical interoperability issues and paving the way for unified configuration methods.

During the All Core Developers Consensus (ACDE) Call #215 on July 3, teams traced the low success rate to fork-ID miscalculations in Besu, mishandling of four-byte identifiers by Nethermind, and sync failures in EL/CL Nimbus implementations.

Fork-ID Discrepancies Stall Besu & Nethermind

In-depth logs revealed that Besu’s fork-ID arithmetic deviated from the canonical spec, causing it to reject valid peer announcements. Meanwhile, Nethermind’s client library misinterpreted four-byte chain identifiers, leading to frequent disconnects.

These errors compounded in Devnet 2’s network mesh, forcing many nodes to stall before finalizing any blocks.

Nimbus Clients Unable to Sync

The most severe interoperability gap emerged with Nimbus, whose EL/CL hybrid nodes failed to sync in Devnet 2. Errors in beacon root validation caused the client to drop peers continuously, rendering Nimbus effectively offline.

Adoption of eth_config JSON-RPC for Genesis Parameters

To prevent future discrepancies, the community has agreed to adopt the standardized eth_config JSON-RPC method introduced by EIP-7910 for fetching genesis parameters such as gas schedules, blob limits, and network forks. This approach replaces ad-hoc client-side objects with a single authoritative source, ensuring every client interprets core parameters identically.

Conclusion

In light of these findings, the role of Devnet 2 has been officially rebranded as a “bug-hunt” sandbox, dedicated to uncovering edge-case failures. Devnet 3 will serve as a “happy-path” stress-test environment under near-production conditions, validating finalized EIP scopes—most notably the doubled contract size limit in EIP-7907 and the six-blob cap from EIP-7594.

Devnet 3 is scheduled for mid-July, with participants encouraged to integrate the eth_config RPC and latest client patches before joining the network.

If you find any issues in this blog or notice any missing information, please feel free to reach out at yash@etherworld.co for clarifications or updates.

Related Articles

  1. EIPs Included in Fusaka Devnet 2: What to Expect?
  2. Ethereum Prepares Validator Custody Rollout with Fusaka Devnet 2
  3. Ethereum Considers 45 Million Gas Limit for Fusaka Upgrade
  4. History Expiry Moves Forward in Ethereum’s Fusaka Upgrade
  5. A Closer Look at What’s Coming in Fusaka Devnet 2
_____________________________________________________________________

Disclaimer: The information contained in this website is for general informational purposes only. The content provided on this website, including articles, blog posts, opinions, and analysis related to blockchain technology and cryptocurrencies, is not intended as financial or investment advice. The website and its content should not be relied upon for making financial decisions. Read full disclaimer and privacy Policy.

For Press Releases, project updates and guest posts publishing with us, email to contact@etherworld.co.

Subscribe to EtherWorld YouTube channel for ELI5 content.

Share if you like the content. Donate at avarch.eth.

You've something to share with the blockchain community, join us on Discord!

Follow us at Twitter, Facebook, LinkedIn, and Instagram.