Block builder must include all storage slots individual txs will access This is consensus critical, so mismatching BAL lists will fail block validation ExecutionPayloadV4 adds a blockAccessList field thats a RLP encoded BAL (So engine API gets a bump) The builder has 2 phases: Collection phase and Build phase. Collection just records all touched state accesses. Build phase is encoding this info in RLP for consumption. BALs should include the following:Address wtih any state changes (storage, balance, nonce or code) Addresses accessed without state changes:targets of balance/extcodesize/extcodecopy/extcodehash opcode targets of call, callcode, delegatecall, staticcall target of create/create2 tx sender and recipient (even for 0 value) coinbase addy when receiving tx fees
11/28/2025:::info :mega: bal-devnet-0 targets to launch on end of Oct 2025. ::: EIP List for bal-devnet-0 EIP-7928: Block-Level Access Lists :new: Key: :up:, EIP has updated!
11/16/2025:::info :mega: epbs-devnet-0 targets to launch on end of Oct 2025. ::: EIP List for epbs-devnet-0 EIP-7732: Enshrined Proposer-Builder Separation :new: Key: :up:, EIP has updated!
10/6/2025EIP-7594: PeerDAS - Peer Data Availability Sampling [x] Validator custody testing - kurtosis - add validators and verify cgc value changes[x] This can be easy by setting validators to 0x02 credential and make manual deposits [x] MEV workflow testing - flashbots mev relay/ rbuilder [x] payload delivery by every client combo via relay [x] Minimal spec testing [ ] Minimal spec testing with mev workflow
10/3/2025