{"id":17409,"date":"2026-02-18T21:46:35","date_gmt":"2026-02-18T21:46:35","guid":{"rendered":"https:\/\/cryptoted.net\/index.php\/2026\/02\/18\/fusaka-update-transaction-gas-limit-cap-arrives-with-eip-7825\/"},"modified":"2026-02-18T21:46:35","modified_gmt":"2026-02-18T21:46:35","slug":"fusaka-update-transaction-gas-limit-cap-arrives-with-eip-7825","status":"publish","type":"post","link":"https:\/\/cryptoted.net\/index.php\/2026\/02\/18\/fusaka-update-transaction-gas-limit-cap-arrives-with-eip-7825\/","title":{"rendered":"Fusaka Update \u2013 Transaction Gas Limit Cap arrives with EIP-7825"},"content":{"rendered":"


\n<\/p>\n

\n

Starting with the upcoming Fusaka<\/a> hard fork<\/strong>, EIP-7825<\/a><\/strong> introduces a per-transaction gas limit cap of 2\u00b2\u2074 (\u2248 16.78 million gas)<\/strong>.<\/p>\n

This change is already live on Holesky and Sepolia<\/strong>, and will activate on mainnet with Fusaka<\/strong>.<\/p>\n

Developers and users who rely on very large transactions should verify that their contracts and transaction builders conform to the new cap.<\/p>\n

\n

<\/g><\/svg><\/a>Background<\/h2>\n

As Ethereum scales to higher block gas limits and prepares for parallel execution (e.g. EIP-7928<\/a> in Glamsterdam), the Fusaka fork<\/strong> introduces a per-transaction gas limit cap.<\/p>\n

Previously, a single transaction could consume the entire block gas limit (~45 million gas), creating potential DoS risks and preventing parallel execution. EIP-7825<\/strong> establishes a hard upper bound<\/em> of 2\u00b2\u2074 gas per transaction to improve block packing efficiency and pave the way for better parallel processing in future execution environments.<\/p>\n

This cap does not affect the overall block gas limit but only restricts how much gas a single transaction may use. In practice, this ensures that blocks consist of multiple smaller, more predictable transactions instead of one very large one.<\/p>\n

\n

<\/g><\/svg><\/a>Impact<\/h2>\n

For most users, nothing changes. The vast majority of transactions are already well below 16 million gas [0]<\/a>.<\/p>\n

However, certain contracts and deployment scripts<\/strong>, particularly those performing batch operations<\/strong>, may exceed this limit. Such transactions will be invalid once Fusaka activates.<\/p>\n

If you maintain infrastructure that generates transactions close to the previous block gas limit, you should:<\/p>\n

    \n
  1. Simulate transactions<\/strong> against Holesky<\/strong> or Sepolia<\/strong>, both of which already enforce the 2\u00b2\u2074 cap.<\/li>\n
  2. Refactor batch operations<\/strong> into smaller, sequential transactions if needed.<\/li>\n
  3. Pre-signed transactions<\/strong> may need to be re-signed using a lower gas limit if the transaction’s gas limit exceeds the new limit.<\/li>\n
  4. Verify tooling<\/strong>, especially contract deployers, routers, and batching scripts, to ensure gas usage remains below the new cap.<\/li>\n<\/ol>\n
    \n

    See [1]<\/a> for an empirical impact analysis.<\/p>\n<\/blockquote>\n

    The new transaction gas limit cap does not affect the limits for eth_call<\/span>.<\/p>\n

    \n

    <\/g><\/svg><\/a>Actionable Changes<\/h2>\n