EIP-7976 Higher calldata floor cost (Increase Calldata Floor Cost)
No call decision · Fees & gas · EIP status Last Call · created 2025-06-18
Raises the calldata floor cost applied to data-heavy transactions from 10/40 gas per byte to 64 gas per byte. In the worst case this shrinks block size by about 37%, creating room to raise the gas limit.
Why it is needed
Ethereum block size is bounded by the gas limit, but a transaction that carries more data (calldata) than computation can produce a much larger block for the same gas. EIP-7623 previously introduced a floor cost of 10/40 gas per byte for data-heavy transactions to shrink the maximum block size, but continued demand to raise the gas limit further has made additional adjustment necessary. At the current floor cost, data-heavy transactions can still produce relatively large payloads, which is a source of block size variance. According to the source, at a price of 64 gas per byte, an uncompressed 10 MiB execution payload would require about 671 million gas. At the existing 10/40 price, about 105 million gas was sufficient. Raising the cost of filling a block with data this way creates a safety margin that can be used to raise the gas limit.
What changes
Today
- Data-heavy transactions pay a floor cost of 10 gas per byte (zero byte) / 40 gas per byte (non-zero byte) of calldata
- The maximum execution payload size is about 1.07 MB (45,000,000/40)
- Large data payloads increase block size variance, making it harder to raise the gas limit
After EIP-7976
- Data-heavy transactions pay a floor cost of 64 gas per byte of calldata, with no distinction between zero and non-zero bytes
- The maximum data-heavy payload size shrinks by about 37% to roughly 0.67 MB (45,000,000/64)
- Ordinary transactions dominated by EVM computation continue to pay 4/16 gas per byte as before
- There is now a stronger incentive to use blobs instead of calldata for data storage
Who is affected
- Ordinary users: Transactions centered on EVM computation, such as DeFi and token transfers, are unaffected, and once wallets and RPCs are updated, existing usage patterns can continue unchanged.
- Wallet and RPC developers: eth_estimateGas MUST be updated to reflect the new TOTAL_COST_FLOOR_PER_TOKEN value of 16. Otherwise it may underestimate gas and cause transactions to fail.
- Users of data-heavy transactions: Transactions that carry large amounts of data in calldata become more expensive. Analysis from September 2024 to September 2025 found that 1.5% of all transactions fall into this category.
- Client teams and node operators: In the worst case, block size shrinks, easing propagation and processing burden and leaving room to consider raising the block gas limit.
In depth
Gas formula: the maximum of the standard cost and the floor cost
Transaction gas is defined as tx.gasUsed = 21000 + max(STANDARD_TOKEN_COST * tokens_in_calldata + execution_gas_used + isContractCreation * (32000 + INITCODE_WORD_COST * words(calldata)), TOTAL_COST_FLOOR_PER_TOKEN * floor_tokens_in_calldata). tokens_in_calldata is zero_bytes_in_calldata + nonzero_bytes_in_calldata * 4, and floor_tokens_in_calldata is (zero_bytes_in_calldata + nonzero_bytes_in_calldata) * 4. execution_gas_used is the gas spent on EVM execution minus gas refunds, and INITCODE_WORD_COST is 2 as defined by EIP-3860. In other words, the left-hand term is today's standard charge, and the right-hand term is the new floor.
Constant values and the conversion to 64 gas per byte
The parameters are STANDARD_TOKEN_COST = 4 and TOTAL_COST_FLOOR_PER_TOKEN = 16. For the floor cost, since floor_tokens_in_calldata is the byte count multiplied by 4, TOTAL_COST_FLOOR_PER_TOKEN * 4 = 64, so both zero and nonzero bytes cost 64 gas per byte. Under EIP-7623 the floor cost was 10/40 gas per zero/nonzero byte, so this is a 6.4x increase for zero bytes and a 1.6x increase for nonzero bytes. The source states that token abstraction is kept not because it is strictly necessary for the computation but solely for consistency with EIP-7623.
Gas limit validity rule
If the gas limit is lower than 21000 + TOTAL_COST_FLOOR_PER_TOKEN * floor_tokens_in_calldata, or lower than the intrinsic gas cost (whichever is larger), the transaction is invalid. This is because a transaction must be able to cover the floor price of its calldata regardless of the execution outcome. There are normal cases where the actual gasUsed comes out below this floor, but the floor price must still be reserved in the gas limit ahead of time. If a wallet sets the gas limit too low, the transaction is rejected before execution even runs, which makes accurate estimation logic important.
Maximum block size reduced by about 37%
Under the EIP-7623 regime, data-heavy transactions pay 10/40 gas per zero/nonzero byte, and the maximum execution layer payload is about 1.07MB (45,000,000/40). This EIP reduces that to about 0.67MB (45,000,000/64). Taking an uncompressed 10MiB execution payload as the baseline, the gas required rises from about 105 million at the 10/40 price to about 671 million at the 64/64 price. The source explains that this reduces the data-heavy maximum payload by about 37%, creates room to raise the block gas limit, and further encourages the use of blobs for data availability purposes.
Real-world scope of impact: 1.5% of transactions
Analyzing blocks 20644414 through 23272414 (September 2024 through September 2025), the source states that an estimated 1.5% of all transactions would be affected by this change. Transactions with enough EVM computation have a standard cost of 4/16 gas per byte that exceeds the floor cost, so they are charged the same as today, meaning common use cases like DeFi or token transfers are unaffected. An empirical analysis report covering the impact (eip7976_empirical_analysis.md) is provided as an asset in the EIP repository.
Backwards compatibility: required action by wallets and nodes
This change is a backwards-incompatible gas repricing that requires a scheduled network upgrade. Wallets must accurately reflect the changed TOTAL_COST_FLOOR_PER_TOKEN value of 16 when using eth_estimateGas, or they may underestimate gas and cause transactions to fail. Node software must also reflect the formula with the new floor cost in RPC methods such as eth_estimateGas. Once this update is made, users do not need to change how they operate.
Security considerations: the bundling issue remains unchanged
The source states that, since the maximum block size is only reduced further compared to EIP-7623, there are no new security concerns beyond what was already addressed in the original proposal. Considerations around bundling multiple transactions together to avoid the floor cost are the same as under EIP-7623. Bundling was possible before and remains possible now, but it does not undermine the goal of reducing block size, and practical constraints around trust and coordination continue to limit how widespread bundling can become. The higher floor cost strengthens the incentive to choose an appropriate data availability method, without opening any new attack vector.
Progress status
The source's status is Last Call, with a last-call-deadline listed as 2026-11-01. Last Call is the final review stage before Final status, so the specification is not yet finalized. The proposal was created on 2025-06-18 and is a Core standards track proposal that requires EIP-7623. The accompanying core developer call records contain no fork-inclusion decision for this EIP.