# Prototyping EIP-7782 (6 second slots) ## Summary 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: ```console kurtosis run github.com/morph-dev/ethereum-package@eip7782 \ --image-download always \ --args-file eip7782.config.yaml \ --enclave eip7782 ``` Where `eip7782.config.yaml` is given below: ```yaml participants: - el_type: geth el_image: morphdev1803/geth:eip7782 cl_type: prysm cl_image: jihoonsg/prysm-beacon-chain-eip7782:0332af5 vc_type: prysm vc_image: jihoonsg/prysm-validator-eip7782:0332af5 count: 3 network_params: genesis_delay: 20 electra_fork_epoch: 0 fulu_fork_epoch: 0 eip7782_fork_epoch: 1 perfect_peerdas_enabled: true num_validator_keys_per_node: 256 ethereum_genesis_generator_params: image: morphdev1803/genesis-generator:eip7782 dora_params: image: morphdev1803/dora:eip7782 additional_services: - dora - tx_fuzz snooper_enabled: true ``` ## Changes ### Consensus Spec update https://github.com/ethereum/consensus-specs/pull/4484 ### Execution Spec update https://github.com/ethereum/execution-specs/pull/1411 ### Geth prototype https://github.com/morph-dev/go-ethereum/tree/eip7782 - Docker image: `morphdev1803/geth:eip7782` - built with: ```console docker buildx build -t morphdev1803/geth:eip7782 . ``` ### Prysm prototype https://github.com/jihoonsong/prysm/tree/eip7782 - Docker images: `jihoonsg/prysm-beacon-chain-eip7782:0332af5` `jihoonsg/prysm-validator-eip7782:0332af5` ### Genesis Generator update https://github.com/morph-dev/ethereum-genesis-generator/tree/eip7782 - Docker image: `morphdev1803/genesis-generator:eip7782` - built with: ```console docker build -t morphdev1803/genesis-generator:eip7782 . ``` ### Dora update https://github.com/morph-dev/dora/tree/eip7782 Required modifying `ethwallclock` go module ([changes](https://github.com/morph-dev/ethwallclock/tree/schedule)). - Docker image: `morphdev1803/dora:eip7782` - built with: ```console docker build -t morphdev1803/dora:eip7782 . ``` ### Kurtosis package update https://github.com/morph-dev/ethereum-package/tree/eip7782 Can be used directly with command like this: ```console kurtosis run github.com/morph-dev/ethereum-package@eip7782 --args-file <config_file> --enclave <name> ```
Last changed by  
 
milos.stankovic@ethereum.org
383

Read more

Implementing Payload Chunking (EIP-8101) in EL

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/2026
Finalized Chain History Portal subnetwork

The 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
Portal network roadmap

Insipired by Vitalik's Ethereum roadmap, I tried to create Portal Network roadmap. It was quickly sketched during Devcon planning meeting, and it's mainly focused on the next 6-12 months of upcoming work of the trin team. This is done purely for fun purposes. If anybody desires, we can explore this idea further and make the actual roadmap.

11/28/2024
Read more from milos.stankovic@ethereum.org
Published on HackMD