As Ethereum moves closer to the highly anticipated Fusaka upgrade, core developers are actively assessing a major enhancement: increasing the network’s gas limit to 45 million per block. This proposed change represents one of the most significant throughput improvements since the Merge and is being rigorously tested across multiple client implementations to ensure stability, safety, and consistent validator performance.
The goal? To boost Ethereum’s capacity without compromising decentralization or security—balancing scalability with long-term sustainability.
Why the Gas Limit Matters
The gas limit determines how much computational work can fit into a single Ethereum block. Think of it as the maximum size of a data package a block can carry. By raising this cap, more transactions, smart contract executions, and Layer 2 data (especially blob-carrying transactions) can be processed per 12-second slot.
Currently, Ethereum’s default gas limit sits around 30 million. However, with the growing demand from Layer 2 rollups and data-heavy applications—particularly those leveraging blob transactions—the network is approaching its limits. A controlled increase to 45 million could significantly improve efficiency and reduce congestion during peak usage.
👉 Discover how blockchain scalability is evolving in 2025.
However, higher gas limits come with trade-offs. Larger blocks place greater strain on node operators, especially validators running consumer-grade hardware. This raises concerns about validator centralization, where only well-resourced participants can keep up, undermining Ethereum’s decentralized ethos.
Thus, any increase must be carefully benchmarked—not just for speed, but for long-term network health.
Client Readiness for the 45M Proposal
For a network-wide change like this, consensus among Ethereum client teams is essential. During recent interop testing and performance benchmarking sessions, major clients shared their progress:
- Geth: The most widely used Ethereum client requires one final fix to support 45M gas. Developers emphasize that exceeding this threshold would necessitate repricing heavy operations like
modexp, which is already addressed in Fusaka via EIP-7883. For now, Geth considers 45 million a safe upper boundary. - Nethermind: Fully supportive of signaling readiness for 45M. While a new release is planned, the current version is stable enough to participate in early tests.
- Erigon: Already prepared for 45 million gas and reports no anticipated issues under the proposed parameters.
This alignment across key clients signals a soft consensus: 45 million gas is achievable without immediate changes to other EVM opcodes—provided all teams integrate necessary performance optimizations in upcoming releases.
Performance Bottlenecks Identified
Even with client readiness, scaling isn’t just about raising a number—it’s about ensuring the entire system can handle the load. Benchmarking efforts have uncovered several critical bottlenecks:
1. ModExp Remains a Key Constraint
Modular exponentiation (modexp) is computationally expensive and has historically slowed block execution. Fortunately, EIP-7883 (part of Fusaka) adjusts its gas cost to better reflect real-world execution time, reducing the risk of denial-of-service attacks and improving overall throughput.
2. Alt\_bn128 Precompiles May Become Next Bottleneck
Cryptographic functions like EC_ADD, EC_MUL, and EC_PAIRING—used heavily in zero-knowledge proofs (ZKPs)—are now under scrutiny. As ZK-based applications grow, these precompiles could become new performance hotspots. Developers are expanding stress tests to evaluate their impact under high-load scenarios.
3. EVM Logs and devp2p Message Limits
When blocks generate massive volumes of logs, they risk exceeding the 10MB message size limit in Ethereum’s devp2p protocol. This could disrupt peer-to-peer synchronization, especially in blocks exceeding 65 million gas (a future possibility). Potential solutions include repricing log operations or upgrading the messaging layer itself.
4. Geth’s Cache Flush Latency Issue
A newly identified issue in Geth involves state tree buffer overflow. Blocks with heavy storage writes can surpass the client’s 256MB memory buffer, triggering synchronous disk flushes that delay block propagation by up to 2.5 seconds.
To address this, Geth developers have proposed an asynchronous double-buffering mechanism, allowing one buffer to accept writes while the other flushes to disk in the background. This fix will be tested in upcoming shadowfork and perfnet environments.
👉 See how next-gen blockchain networks are solving performance challenges.
What’s Next: Path to Mainnet Implementation
Over the coming weeks, client teams will focus on integrating performance patches and validating them in test environments—particularly during Fusaka Devnet 2, which serves as a critical proving ground.
The primary objective? Establish 45 million gas as a new safe default across all clients. If successful, this could lead to a formal proposal for mainnet adoption.
However, final approval depends on three key factors:
- Broad agreement among client teams
- Consistent benchmark results showing no execution regressions
- Evidence that validator performance remains stable across diverse hardware setups
There is no rush—Ethereum prioritizes stability over speed. But if Devnet 2 confirms feasibility, we could see the first steps toward higher throughput within months.
Frequently Asked Questions (FAQ)
Q: What is the current Ethereum gas limit?
A: The default gas limit is approximately 30 million per block, though it can fluctuate slightly based on network conditions.
Q: Why increase to 45 million specifically?
A: This level balances increased throughput with manageable execution load. It supports growing L2 data needs without requiring immediate opcode repricing beyond what’s already planned in Fusaka.
Q: Could a higher gas limit lead to centralization?
A: Yes—that’s a core concern. Larger blocks require more processing power and bandwidth, potentially favoring institutional validators over individual operators. That’s why extensive testing is underway.
Q: Is this change part of the Fusaka upgrade?
A: While not officially confirmed yet, increasing the gas limit is being evaluated alongside Fusaka improvements like EIP-7883 and blob data optimizations.
Q: When might this go live on mainnet?
A: There’s no set timeline. Success in Devnet 2 could pave the way for a proposal later in 2025, pending full client consensus and security review.
Q: How does this affect Layer 2 networks?
A: Higher gas limits allow L2s to post more data per block, reducing fees and improving transaction finality—direct benefits for end users.
Conclusion
The move toward a 45 million gas limit reflects Ethereum’s maturing infrastructure and growing confidence in client optimization. While still in testing phases, this upgrade could mark a pivotal step in scaling Ethereum’s computational capacity—supporting richer applications, lower fees, and broader adoption.
Fusaka Devnet 2 will be the decisive test. If results confirm stability across clients and hardware profiles, Ethereum may unlock new levels of performance ahead of even more ambitious targets—such as 60M or 100M gas—in future upgrades.
For now, developers remain cautious but optimistic: scalability must never come at the cost of decentralization.
👉 Stay ahead of blockchain innovation—explore tools built for the future of Web3.