The Ethereum community is gearing up for Fusaka Devnet 3 after valuable lessons from Devnet 2 testing. This next phase will validate critical consensus enhancements under realistic network conditions.

• EIP Repricing & Consensus Tweaks
• Code Size Indexing & Stateless Support
• Performance Benchmarking & Interop Goals
• Conclusion

EIP Repricing & Consensus Tweaks

Developers will revisit EIP-7907 to adjust gas costs for ultra heavy transactions above sixty million gas units. The goal is to calibrate fees so that complex contracts remain viable without exposing the network to resource exhaustion.

Teams are proposing both incremental increases and bolder adjustments to better reflect actual execution costs. In parallel, consensus parameters such as target block gas limits will be fine tuned to ensure stability under peak load.

Code Size Indexing & Stateless Support

To empower stateless clients, the community is debating how to index contract code size. One approach embeds a standardized index into consensus rules so nodes can verify code size without storing full state.

Another leverages out-of-protocol lookups to avoid bloating on-chain data. Proponents of the embedded index argue it streamlines light client operation while critics warn of added consensus complexity.

A formal decision will be made at the Devnet 3 spec freeze following dedicated protocol workshops.

Performance Benchmarking & Interop Goals

A unified benchmark suite will simulate real-world scenarios from rapid bulk contract deployments to MEV-style relay workflows. Metrics will include sync times, block propagation latency, memory usage, and error rates.

Results will feed a public dashboard giving each client team transparency into strengths & weaknesses. The aim is to reach performance parity across implementations before mainnet rollout preparations begin.

Conclusion

Devnet 3 will give Ethereum core devs the opportunity to identify and resolve issues before they reach mainnet. Focusing on realistic gas cost adjustments, reliable code indexing, and robust performance testing will help each client meet Fusaka’s demands.

By testing together and sharing results, core devs can launch this upgrade with confidence in its stability and interoperability.

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.