Starting with the next Fusaka hard fork, EIP-7825 introduced a gas limit cap per transaction of 2²⁴ (≈ 16.78 million gas).
This change is already live on Holesky and Sepoliaand will activate on mainnet with Fusaka.
Developers and users who rely on very large transactions should verify that their contracts and transaction generators comply with the new cap.
Background
As Ethereum moves toward higher block gas limits and prepares for parallel execution (e.g. EIP-7928 in Glamsterdam), the Fusaka fork introduces a gas limit cap per transaction.
Previously, a single transaction could consume the entire block gas limit (around 45 million gas), creating potential DoS risks and preventing parallel execution. EIP-7825 establishes a strict upper limit of 2²⁴ gas per transaction to improve block clustering efficiency and pave the way for better parallel processing in future execution environments.
This cap does not affect the overall block gas limit, but only restricts the amount of gas a single transaction can use. In practice, this ensures that blocks are made up of several smaller, more predictable transactions instead of one very large one.
Impact
For most users, nothing changes. The vast majority of transactions are already well below 16 million gas (0).
However, some contracts and deployment scriptsespecially those who perform batch operationsmay exceed this limit. Such transactions will be invalid once Fusaka is activated.
If you maintain infrastructure that generates transactions close to the previous block’s gas limit, you should:
- Simulate transactions against Trousky Or Sepoliaboth of which already apply the 2²⁴ cap.
- Refactor batch operations into smaller, sequential transactions if necessary.
- Pre-signed transactions It may be necessary to re-sign using a lower gas limit if the transaction’s gas limit exceeds the new limit.
- Check the toolingespecially contract deployers, routers and batch scripts, to ensure gas consumption stays below the new cap.
See (1) for an empirical impact analysis.
The new transaction gas limit cap does not affect limits for eth_call.
Actionable Changes
- Test deployments and transaction generators on Sepolia Or Trousky.
- Adjust any gas estimation logic that assumes a higher per-transaction limit.
- Update monitoring and alert systems to flag transactions exceeding the new gas limit.
All major client implementations (Geth, Erigon, Reth, Nethermind, Besu) have included this change in their Releases ready for Fusaka.
Outlook
The per-transaction gas limit cap is part of Ethereum’s ongoing transition to parallel execution. While this may require adjustments, it sets a safer and more predictable foundation for higher throughput in future forks.
Developers and ecosystem teams are encouraged to test on public test networks before mainnet activation and to follow discussions in All Core developers And Ethereum Magicians for the next EIPs.
The full discussion and rationale for the gas limit introduced in EIP-7825 can be found in (2).
A PEEPanEIP episode with Jules of Erigon is located in (3).
References
(0)
(1)
(2)
(3)
