Ethereum
Ethereum proposal would add bytecode reads to block access lists
A proposal published by Lukasz Rozmej on November 12 would identify existing bytecode a block needs. It would change the execution data committed to in the block header.

Existing code is missing from the list
On November 12, Lukasz Rozmej opened a proposal on block-level access lists, or BALs, defined by EIP-7928. These lists record the accounts and storage locations used during execution, along with certain state changes. An entry records a contract’s bytecode when it changes. An address whose code is simply called or inspected is already listed, but its entry can look the same as that of an account whose balance was checked.
The draft would add a seventh field, code_hash, to each account entry. It would contain the Keccak-256 hash of the bytecode present at the start of the block if that code is nonempty and the block performs a recognized read for that account. The field would be empty otherwise. The proposal covers code that predates the block. The information needed to reconstruct code created during the block comes from executing that block, even if a creation is later reverted.
Which operations would populate the field
The draft counts operations including calling a contract and running EXTCODESIZE and EXTCODECOPY, which inspect the size of the bytecode or copy it. Checking a balance on its own leaves the field empty. The same applies to EXTCODEHASH, which can be resolved from the hash already associated with the account. The rule follows protocol operations. A client that prefetches bytes to save time would not record that technical read in the list.
The proposal also distinguishes the code of a delegated account from the code of its target. For an account using EIP-7702 delegation, the code at the start of the block may be the delegation indicator itself. If the execution rules then load the target’s code, the target can have its own populated entry. The draft also describes interrupted calls. A failure after access can leave the read in the list. An operation that fails its gas check before access does not record that access.
Preparing proofs under specific conditions
For a service building a proof, the field would provide a reference for finding the bytecode in storage indexed by hash. Accounts sharing code could then use a single copy in the data needed for verification. The draft says EIP-7709 would also have to be active to assemble all these data without first executing the block. It would put the data needed by the BLOCKHASH instruction among the recorded storage reads.
A populated field would add 33 bytes to the RLP-encoded entry, compared with one byte for an empty field, before any extra bytes in length prefixes. That encoding would feed into the hash of the list committed to in the block header. Activating the rule would therefore require an upgrade incompatible with older clients. Rozmej’s text remains a draft. The November 12 submission documents the proposed mechanism and its test cases.
