The debate around increasing Ethereum's gas limit—whether through raising the cap or reducing slot times—is gaining momentum. With network demands evolving and validator hardware requirements steadily decreasing over the past four years, many are asking: Is it finally time to revisit Ethereum’s gas limit? This article dives deep into the technical implications of doubling the gas limit, analyzing potential impacts on bandwidth, computation, and storage. We’ll also explore two key proposals—EIP-7783 and EIP-7782—and assess their feasibility in today’s ecosystem.
Ethereum’s Gas Limit: A Historical Overview
When Ethereum launched in 2015, the initial gas limit was set at 5,000 gas per block. Since then, it has undergone several significant increases:
- 2016: Raised to approximately 3 million, then later to 4.7 million.
- Post-Tangerine Whistle hard fork: Increased to 5.5 million following EIP-150, which re-priced I/O-heavy opcodes in response to DoS attacks.
- July 2017: Raised to 6.7 million.
- December 2017: ~8 million.
- September 2019: ~10 million.
- August 2020: 12.5 million.
- April 2021: 15 million.
Under EIP-1559, a hard cap was introduced—twice the target limit—allowing blocks to contain up to 30 million gas during peak demand. However, for nearly four years, no further increases have been implemented.
👉 Discover how blockchain scalability evolves with network upgrades
Evaluating the Need for a Higher Gas Limit
To determine whether now is the right time for an increase, we must assess the impact on three core resource areas: storage, bandwidth, and computation—especially under a scenario where the gas limit is doubled to 60 million.
Storage: Not the Primary Bottleneck
Storage has long been considered a major constraint due to Ethereum’s growing state size. The network maintains two types of data growth:
- State growth: The cumulative size of account balances, smart contract code, and storage.
- Historical growth: The accumulation of past blocks and transaction data.
State Growth Analysis
Currently, Ethereum’s state grows at about 2.5 GB per month (30 GB/year). While this expansion can lead to:
- Slower disk access times
- Higher hardware requirements for validators
These concerns are largely mitigated by modern hardware advancements. Due to logarithmic algorithmic complexity in state queries, performance differences across storage systems remain negligible—even with tens of gigabytes of variation. Additionally, SSD prices continue to drop exponentially, far outpacing state growth.
Even if state growth doubled to 60 GB/year, technological progress in storage hardware would likely absorb the added burden without issue.
Historical Growth and Future Storage Needs
Looking ahead, independent validators may soon require over 2TB of storage, effectively pushing them toward 4TB drives (due to standard hardware configurations based on powers of two). This means that extra storage capacity from a higher gas limit could be efficiently utilized, as validators are already investing in high-capacity drives regardless.
Note: There is no meaningful average vs. worst-case analysis for storage, as sustained high-load block processing over weeks or months remains prohibitively expensive.
Storage Cost Trends Over Time
Historical data shows that SSD prices halve approximately every two years. Compared to Ethereum’s linear state growth, this exponential decline in storage costs makes long-term scalability more manageable. Even without advanced optimization techniques like stateless clients or pruning, hardware evolution alone supports moderate gas limit increases.
Bandwidth: The Real Challenge
While storage is manageable, bandwidth presents a more pressing concern—especially during peak usage.
Average Case Scenario
Ethereum currently averages around 2MB/s in bandwidth usage. Most of this stems from block propagation and attestation aggregation. The largest recorded block size is 270 KB, while post-Deneb average blocks sit around 75 KB.
Doubling the gas limit would increase block sizes proportionally:
- From 75 KB → ~150 KB (average)
- From 270 KB → ~540 KB (peak)
This translates to only a 2–5% increase in node bandwidth requirements—manageable for most modern networks. In fact, adding just three extra blobs per block would impose a greater strain than doubling calldata under current conditions.
Worst-Case Scenario: 2x Gas Limit
In worst-case modeling, a fully packed block could reach 1.7MB, increasing to 3.4MB under a doubled limit—requiring a +50% spike in peak bandwidth.
However, launching such an attack is prohibitively expensive:
- Filling consecutive blocks with 30 million gas each demands massive capital.
- Attackers must outbid legitimate users for inclusion, further increasing costs.
- Network economics inherently discourage sustained DoS attempts.
Moreover, any bandwidth-related risks can be mitigated through calldata cost adjustments, making this threat largely theoretical—especially when combined with gradual increases via EIP-7783.
👉 Explore how transaction efficiency shapes blockchain performance
Computation: Minimal Risk Under Normal Conditions
Computation has historically not been a bottleneck—but let’s examine both average and worst-case scenarios.
Average Case
Block processing typically takes less than one second, even on slower machines with degraded disks. For typical workloads, computation is not a limiting factor.
Worst-Case Considerations
Some opcodes—like MODEXP (modular exponentiation)—do not scale efficiently and could be exploited for DoS attacks. However:
- These vulnerabilities can be addressed through opcode re-pricing.
- Client teams agree that such edge cases are manageable.
- With EIP-7783’s incremental approach, computational risks remain negligible.
Key Proposals: EIP-7783 vs. EIP-7782
Two main proposals have emerged for increasing throughput:
EIP-7783: Gradual Gas Limit Increase
This proposal introduces a mechanism for slowly increasing the gas limit over time, avoiding sudden spikes in network load. Benefits include:
- Controlled adaptation by node operators
- Reduced risk of DoS or centralization pressure
- Compatibility with existing infrastructure
Given its cautious design, EIP-7783 makes a 33% increase—or even a full doubling—of the gas limit feasible today.
EIP-7782: Reducing Slot Time
This proposal suggests shortening the slot duration from 12 seconds to potentially 8 or 6 seconds, effectively increasing block frequency.
However, implementing EIP-7782 now could negatively impact:
- Distributed Validator Technology (DVT)
- Single Secret Leader Election (SSF)
These systems rely on predictable timing and coordination windows. Premature reduction could degrade finality and increase proposer failure rates.
Verdict: While reducing slot time is a promising long-term goal, now is not the right time for implementation.
Frequently Asked Questions (FAQ)
Q: Why hasn’t Ethereum increased its gas limit in four years?
A: Stability and decentralization were prioritized. Developers wanted to ensure network resilience after major upgrades like The Merge and Dencun before adjusting core parameters like gas limits.
Q: Would doubling the gas limit make transactions cheaper?
A: Not necessarily. While more space per block could ease congestion temporarily, fee levels depend on demand. Without proportional user growth, fees may only see modest reductions.
Q: Does higher gas mean worse decentralization?
A: Potentially—but only if hardware demands outpace consumer tech trends. Current analysis suggests storage and bandwidth impacts remain within acceptable bounds.
Q: How does EIP-7783 prevent abuse?
A: By incrementally raising the cap, it allows nodes to adapt gradually and gives developers time to respond to unexpected issues—reducing systemic risk.
Q: Can calldata pricing solve bandwidth issues?
A: Yes. Adjusting calldata costs based on actual network strain (e.g., via EIP-4488 or similar) would disincentivize bloated transactions and protect bandwidth.
Q: What’s the safest way forward?
A: Implement EIP-7783 first with a moderate increase (e.g., +33%), monitor network behavior, then consider further steps—including eventual slot time reductions once DVT/SSF mature.
Final Thoughts
After thorough analysis, storage growth is not a critical bottleneck—thanks to rapidly declining hardware costs and predictable linear growth. Bandwidth poses a greater challenge, but even worst-case scenarios are economically constrained and technically manageable.
With EIP-7783 offering a safe path forward through gradual adjustment, there’s strong justification for increasing Ethereum’s gas limit—potentially by 33% or even doubling it today.
EIP-7782, while promising, should wait until DVT and SSF ecosystems stabilize. For now, incremental improvement beats aggressive change.
👉 Stay ahead with real-time insights on Ethereum network upgrades