Here’s the altered content, where the original text has been rewritten while maintaining its core information:
With the forthcoming Fusaka hard fork, EIP-7825 will implement a gas limit cap of 2²⁴ (approximately 16.78 million gas) per transaction.
This update is currently operational on Holesky and Sepolia and is set to go live on mainnet with the Fusaka upgrade.
It is crucial for developers and users dealing with large transactions to assess whether their contracts and transaction creators comply with this new gas cap.
Background
As Ethereum advances towards increased block gas limits and gears up for parallel execution (for instance, EIP-7928 in Glamsterdam), the Fusaka fork brings in a cap on gas usage per transaction.
In the past, a single transaction could take up the entire block gas limit (~45 million gas), which presented potential DoS vulnerabilities and hindered parallel execution. EIP-7825 implements a strict upper limit of 2²⁴ gas per transaction, enhancing block packing efficiency and setting the stage for improved parallel processing in future execution environments.
This limitation does not modify the overall block gas limit, but rather limits the gas consumption of individual transactions. This approach ensures that blocks contain a combination of smaller, more manageable transactions instead of a single oversized transaction.
Impact
For the majority of users, there will be no significant changes. Most transactions fall well below the 16 million gas threshold [0].
Nevertheless, some contracts and deployment scripts, notably those handling batch operations, may breach this limit, rendering such transactions invalid once Fusaka is live.
If you manage systems that generate transactions near the previous block gas limit, it is advisable to:
- Test transactions on Holesky or Sepolia, both of which already impose the 2²⁴ restriction.
- Break down batch operations into smaller, sequential transactions if necessary.
- If applicable, re-sign pre-signed transactions to adhere to a lower gas limit if they exceed the new threshold.
- Check your tools, especially contract deployers, routers, and batching scripts, to confirm that gas usage is maintained below the new cap.
Refer to [1] for a detailed impact analysis.
It’s important to note that the new transaction gas limit cap has no impact on eth_call limits.
Actionable Changes
- Conduct testing of deployments and transaction generators on Sepolia or Holesky.
- Modify any gas estimation algorithms that are based on a higher transaction limit.
- Revise monitoring and alert systems to detect transactions exceeding the new gas limit.
All primary client implementations (Geth, Erigon, Reth, Nethermind, Besu) have incorporated this adjustment into their Fusaka-compatible versions.
Outlook
The introduction of the per-transaction gas limit cap is a step in Ethereum’s continuous shift toward parallel execution. While some adjustments may be necessary, this lays a more reliable and predictable foundation for enhanced throughput in future upgrades.
Developers and teams within the ecosystem are encouraged to conduct tests on public testnets ahead of the mainnet transition and actively engage in dialogues on AllCoreDevs and Ethereum Magicians regarding forthcoming EIPs.
For a detailed discussion and reasoning behind the gas limit established in EIP-7825, please visit [2].
Check out a PEEPanEIP episode featuring Giulio from Erigon, available here: [3].
References
[2] https://ethereum-magicians.org/t/eip-7987-transaction-gas-limit-cap-at-2-24/24746
This version has the same information but has been rephrased and adjusted for clarity and readability. The HTML structure remains unchanged.
