web3wagmi
← All standards

EIP-7928 Block-Level Access Lists

ReviewCorecreated 2025-03-3114 later proposals build on it

Enforced block access lists with state locations and post-transaction state diffs

Authors: Toni Wahrstätter (@nerolation), Dankrad Feist (@dankrad), Francesco D`Amato (@fradamt), Jochem Brouwer (@jochem-brouwer), Ignacio Hagopian (@jsign), Felipe Selmo (@fselmo), Rahul (@raxhvl), Stefan (@qu0b)

Built on by (14)

Later proposals that name this one in their requires field.

EIP-2780Resource-based intrinsic transaction gasEIP-8025Optional Execution ProofsEIP-8037State Creation Gas Cost IncreaseEIP-8057Inter-Block Temporal Locality Gas DiscountsEIP-8101Payload Chunking with Chunk Access ListsEIP-8142Block-in-Blobs (BiB)EIP-8146Block Access List SidecarsEIP-8159eth/71 - Block Access List ExchangeEIP-8189snap/2 - BAL-Based State HealingEIP-8268Storage Roots in Block Access ListsEIP-8279Block Access List Byte FloorEIP-8289Multi-block Access List WarmingEIP-8347Offline State Migration to the PBTEIP-8369VOPS Profiles for FOCIL Eligibility

What the specification covers

AbstractMotivationSpecificationBlock Structure ModificationRLP Data StructuresScope and InclusionBlock Access List Size ConstraintGas Validation Before State AccessEIP-7702 DelegationSSTOREOrdering, Uniqueness and DeterminismBlockAccessIndex AssignmentRecording Semantics by Change TypeStorageBalance (balance_changes)CodeNonceEdge Cases (Normative)Engine APIState Transition FunctionConcrete ExampleRationaleBAL Design ChoiceBAL Size Considerations (60m block gas limit)Asynchronous ValidationBackwards CompatibilitySecurity ConsiderationsValidation OverheadBlock SizeEarly Rejection of Malicious BALsCopyright

This proposal declares no Solidity interface, so there is nothing to compute. It may be a core protocol change, a meta proposal, or written in prose only.

Compare with

Parsed from the canonical specification · discussion