In this track: Ethereum protocol concepts
Access list transactions
Declared accesses participate in a specific transaction and gas model.
A work order can list cabinets it expects to open before work begins.
In this simple default-layout example, two uint128 values come before one uint256. Each slot holds thirty-two bytes.
Animated local teaching model. No wallet, RPC or live blockchain data. Some labels and hashes are abbreviated for readability.
Identify the access list
An access list names addresses and storage keys under its transaction format. It is not a list of permissions granting arbitrary access to private data.
Connect to warm-access accounting
Listed accesses affect gas accounting according to the applicable rules. Including a list has its own cost, so it is not universally a free discount.
Do not confuse prediction and restriction
A list of anticipated accesses does not generally constrain execution to only those locations. The code’s behavior and protocol rules still determine what is accessed.
Measure the actual case
Whether a list helps depends on the execution path and state-access pattern. Compare under matching fork and fixture conditions.
Map the protocol concept
access list entry:
address
associated storage keys
Account for list cost and the actual access pattern.A conceptual model. Exact fields, limits and processing rules must be checked against the intended network fork.
Is an access list generally an authorization list limiting every touched slot?
It participates in transaction/gas behavior rather than granting that restriction.
Original explanations by EtherTools. Examples are educational and source-linked; this site is independent of the Ethereum Foundation. Our approach.