EIP-7981 Raising the cost of access lists (Increase Access List Cost)

No call decision · Fees & gas · EIP status Last Call · created 2024-12-27

Adds an extra charge of 64 gas per byte for the data capacity occupied by access lists. This closes a loophole that let blocks be inflated by bypassing the EIP-7623 floor price, cutting the worst-case block size by about 21%.

Why it is needed

An access list is a list that declares in advance which addresses and storage slots a transaction will touch. Currently, adding an entry to this list only costs the storage access fee, with no charge for the data capacity the list itself occupies in the block. The problem is that this lets you bypass the data floor pricing Ethereum introduced with EIP-7623. Because access list costs are counted as EVM gas, mixing calldata and access lists in the right ratio lets you leave a large data footprint without paying the floor price. Using this method, a block can be inflated up to the network's intended maximum. This EIP closes this loophole by charging a per-byte fee on access list data as well. As a result, the worst-case block size shrinks by about 21%, with little impact on ordinary users.

What changes

Today

After EIP-7981

Who is affected

In depth

The new charge item access_list_data_cost

access_list_bytes is the total byte count of the addresses (20 bytes each) and storage keys (32 bytes each) contained in the access list. Multiplying this by 64 gas per byte gives access_list_data_cost. This works out to 1280 gas per address and 2048 gas per storage key. The rate of 64 gas per byte matches the calldata floor rate in EIP-7976. The existing constants ACCESS_LIST_ADDRESS_COST (2400, EIP-2930), ACCESS_LIST_STORAGE_KEY_COST (1900, EIP-2930), and TOTAL_COST_FLOOR_PER_TOKEN (16, EIP-7976) remain unchanged.

Position in the gasUsed formula and validity rules

access_list_data_cost is added as a fixed surcharge outside the max(). That is, tx.gasUsed equals 21000 + access_list_data_cost plus the larger of the execution path cost (STANDARD_TOKEN_COST x tokens_in_calldata + execution_gas_used + contract creation cost + access_list_cost) and the floor cost (TOTAL_COST_FLOOR_PER_TOKEN x floor_tokens_in_calldata). The access_list_cost from EIP-2930 and the floor formula itself from EIP-7976 are not changed. In addition, a transaction whose gas limit is lower than tx.gasUsed evaluated with execution_gas_used set to 0 is treated as invalid.

Design intent: making all data pay the floor rate

Access list data is always charged at the floor rate regardless of how much execution gas is used. This prevents using access lists to bypass the calldata floor price, and applies a consistent price to every source of transaction data, whether calldata or access lists. From a security standpoint, without this fix an attacker could combine access lists and calldata to build blocks larger than intended.

Reference implementation: added to both intrinsic_gas and floor_gas

The reference implementation uses calculate_access_list_data_cost to sum 20 + 32 x len(access.slots) bytes per entry, then multiplies by 64. This surcharge is added to both intrinsic_gas (added to TX_BASE_COST + calldata cost + creation cost + access_list_cost) and floor_gas (added to TX_BASE_COST + floor_tokens_in_calldata x TOTAL_COST_FLOOR_PER_TOKEN). Since the same value is added to both, tx.gasUsed = max(intrinsic_gas + execution_gas_used, floor_gas) produces the same result as the spec's fixed-surcharge approach.

Backward compatibility

Since this is a backward-incompatible gas repricing, a scheduled network upgrade is required. Wallets and nodes need to update their gas estimation logic. Typical usage patterns, however, are barely affected.

Current status and dependencies

This EIP is in Last Call status with a deadline of 2026-11-01. It builds on EIP-2930 (access lists), EIP-7623 (calldata floor price), and EIP-7976 (floor rate constants). No call decision on inclusion in a specific hard fork is recorded in the provided notes.

Original EIP · ← EIPs