As Ethereum progresses toward the Fusaka upgrade, developers are evaluating a potential increase in the network's gas limit to 45 million per block. This change represents one of the most significant throughput adjustments since the post-Merge era. The proposal is undergoing rigorous benchmarking across client implementations to ensure stability, safety, and consistent validator performance.
Why the Gas Limit Matters
The gas limit determines the computational capacity of each block. Raising it allows more data and smart contract activity per slot, potentially improving network efficiency and Layer 2 throughput. However, higher limits also increase execution burdens on clients, raising concerns about validator centralization and attack surfaces.
Ethereum's current default gas limit hovers around 30 million. With the rise of data-heavy operations—particularly blob-related workloads—the community is exploring a controlled increase to 45 million.
Client Positions on the 45M Proposal
During interoperability testing and benchmarking, key client teams reported their readiness:
- Geth: Requires a single fix merged to the master branch. Developers caution that exceeding 45 million would necessitate repricing heavy operations like
modexp, already addressed in Fusaka via EIP-7883. Geth supports 45M as a safe upper limit for now. - Nethermind: Comfortable signaling support for 45M. A new release is planned, but the current version is stable enough for inclusion.
- Erigon: Fully prepared for 45M with no anticipated issues under proposed changes.
This alignment suggests a soft consensus that 45 million is achievable without immediate repricing of other EVM opcodes, provided all clients integrate performance fixes in upcoming releases.
👉 Explore Ethereum's scalability roadmap
Benchmarking Insights
Performance tests identified critical bottlenecks affecting Ethereum's scalability post-Fusaka:
- ModExp (Modular Exponentiation): The primary constraint, slated for repricing under EIP-7823 and EIP-7883, which should reduce its impact on block execution times.
- Alt_bn128 Precompiles: Cryptographic operations (
EC_ADD,EC_MUL,EC_PAIRING) used in zero-knowledge applications may become the next bottleneck. Expanded test cases are underway to assess client performance under load. - EVM Logs and Devp2p Limits: Large log volumes risk overwhelming the 10MB devp2p message cap. Solutions may involve repricing or updates to peer-to-peer messaging layers for blocks exceeding 65 million gas.
- Geth Cache Flush Latency: High storage writes can overflow the 256MB state tree buffer, triggering disk flushes that delay execution by up to 2.5 seconds. An asynchronous flushing mechanism is proposed to mitigate this.
Next Steps for Gas Limit Scaling
Client teams will continue integrating fixes and performance improvements in coming weeks. The primary goal is to validate 45 million gas as the new safe default during Fusaka Devnet 2. If benchmarks confirm network stability, this could form the basis for a mainnet gas ceiling proposal.
The final decision hinges on broad client agreement and demonstrable benchmarks showing the network can handle additional load without execution regressions or validator centralization risks.
Conclusion
The 45 million gas limit proposal reflects Ethereum's growing confidence in client optimization and protocol maturity. Fusaka Devnet 2 will serve as the proving ground for whether Ethereum can safely scale computational capacity ahead of more ambitious targets (e.g., 60M–100M) in future upgrades.
👉 Learn how Ethereum upgrades impact DeFi ecosystems
FAQ
What is the current Ethereum gas limit?
The default gas limit is approximately 30 million per block.
Why raise the gas limit to 45 million?
Higher limits improve throughput for data-heavy operations (e.g., blobs) and Layer 2 scaling, but require careful client optimization.
Which Ethereum clients support the 45M proposal?
Geth, Nethermind, and Erigon have signaled readiness, pending minor fixes.
What are the risks of increasing the gas limit?
Potential risks include validator centralization, client performance bottlenecks, and expanded attack surfaces.
When will the 45M gas limit take effect?
If validated during Fusaka Devnet 2, a mainnet proposal could follow in subsequent upgrades.