# Portal network roadmap Insipired by Vitalik's [Ethereum roadmap](https://x.com/VitalikButerin/status/1741190491578810445), 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. ![](https://storage.googleapis.com/ethereum-hackmd/upload_0cc32e72739b991b21be1d6e14912306.png) This is done purely for fun purposes. If anybody desires, we can explore this idea further and make the actual roadmap.
Last changed by  
 
[email protected]
22

Read more

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:

9/7/2025
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
Read more from [email protected]
Published on HackMD