Increase Calldata Floor Cost to 96

The problem

The whole anchor argument rests on one number: the ETH-transfer block’s byte density of about 0.0104 bytes/gas. That’s meant to be the densest a block can get. But today a block filled entirely with calldata transactions is actually denser than that, so calldata, not the transfer, becomes the binding bandwidth constraint. As long as that’s true, the gas limit can’t be raised to the analysis’s optimum without risking propagation.

What it does

EIP-8311 raises the calldata floor from 64 to 96 gas per byte for data-heavy transactions, while leaving the standard pricing untouched:

Path	Rate	Applies to
Standard	4 / 16 gas per zero / non-zero byte	Computation-heavy txs
Floor	96 gas per byte	When calldata is the binding constraint

A transaction pays max(standard_rate, floor_rate). EVM-intensive transactions keep paying the standard rate and are unaffected; only data-heavy transactions are pushed up to the floor.

Why it matters for scaling

At 96 gas/byte, a pure-calldata block’s byte density drops to roughly 0.0104 bytes/gas, the same as the ETH-transfer line. Calldata is no longer denser than the anchor, so it stops being the bandwidth bottleneck and the gas limit can move to its optimum.

Why these three are the minimal set

EIP	Closes	Without it
8131	Static content under-pricing	Bytes packed cheaper than the limit assumes
8279	Runtime BAL byte bypass	Mixed blocks blow past the bandwidth bound
8311	Calldata denser than the anchor	Calldata stays the binding bandwidth constraint

Each one removes a different way a block could exceed the byte density the higher limit assumes. Together they are the smallest change that lets the limit safely reach 450M.