While working on prototyping Payload Chunking (EIP-8101) in Geth, I noticed several things that I would like to highlight in order to help other developers while implementing the EIP. BAL vs CAL BlockAccessList needs very little modification in order to support ChunkAccessList use cases. In addition to already existing logic, we need to add following functionality: Tracing The AccessListTracer should for reads also keep track of the first tx that created the read. The reads shouldn't be removed if write happens in the later tx (but it's safe not to keep reads if write happened during the same or earlier tx). Buliding Chunk Access List (CAL) With the tracing modification and already existing data, we have enough data to build CAL. One just has to make sure that reads are removed from the CAL if there is a write inside the same chunk (or in any earlier chunk).
1/15/2026Summary The basic implementation of EIP-7782 was built in Geth and Prysm on top of Fusaka fork. In order to run devnet, we modified several other projects: Genesis generator Kurtosis package Dora Devnet can be run with following command using kurtosis:
9/7/2025The Finalized Chain History is the subnetwork build on top of Portal wire protocol. Its goal is to provide decentralized storage of the finalized historical Ethereum data. It assumes that nodes on the network are Execution Layer clients that store all historical headers locally. Nodes that are not Execution Layer clients will need a way to obtain block header for a given block number (in order to verify the content). Specification Distance Function The history network uses the stock XOR distance metric defined in the Portal wire protocol specification. Content id Derivation Function The content keys (described later) use block number. The content id is calculated in the following way:
6/21/2025