# Portal Summit Berlin 2025 The Portal Network's annual in-person summit. Two days of presentations, discussions, and co-working centered on the development and implementation of the Portal protocol. [RSVP Form](https://docs.google.com/forms/d/e/1FAIpQLSeb9XZmd52OQZH0jNG68f_obh3N9_Vc5IIyFDHaL3bmLG4_4g/viewform?usp=dialog) (one response per team) - **When:** March 10th & 11th - **Where:** [Web3 Hub Berlin](https://www.w3hub.berlin/host-events) - Möckernstraße 120, 10963 Berlin, Germany - **Who:** Open to anyone, but focused on technical contributors to the project. ## Topics & Focus ### Execution Client Integration We have multiple execution clients who are in the process of integrating Portal into their client. We will be focused on informational topics surrounding this use case. - JSON-RPC use case - Full Historical Sync use case - Trin experiment: https://github.com/ethereum/trin/pull/1627 - Fluffy experiment: https://github.com/status-im/nimbus-eth1/pull/2910#issuecomment-2650519756 - Discord Conversation: https://discord.com/channels/890617081744220180/890617129425047583/1338850654017421374 ### Full 4444s with rolling HEAD window Lets talk about plans for this. ### State Network Go-live @Kolby and @Milos will cover this. ### Protocol Upgrades - [Native DiscV5 Connections for uTP](https://github.com/ethereum/devp2p/issues/229) - [Rendevous Protocol](https://github.com/ethereum/devp2p/issues/207) - Large Node architecture ### Support For New Logs API EIP: https://eips.ethereum.org/EIPS/eip-7745 Etan Talk: https://www.youtube.com/watch?v=uoCNpufygBE ### Large Object Storage aka "Torrenting" Piper Storing large SSZ objects in Portal, using Merkle indices to evenly distribute un-evenly sized SSZ objects. Use case of dense archival state storage. ### Roadmap Planning - Plan for the week (early on first day) - Plan for the network (midday on the second day) ## Agenda ### Monday March 10th - Day 1 of 2 - **0900 - 1000:** - Doors open. Coffee and breakfast available - **1000 - 1100:** - Portal Network in 45 minutes or less - Piper Merriam - **1135 - 1150:** - Agenda review and revision - **1150 - 1220:** - Execution client use cases. JSON-RPC and sync. Discussion - **1220 - 1320:** - Lunch - **1320 - 1400:** - State Network Deep Dive and Roadmap - **1400 - 1430:** - Portal Roadmap for 2025 - **1430 - 1500:** - Afternoon Break - **1500 - 1600:** - Full 4444s with rolling HEAD window. ### Tuesday March 11th - Day 2 of 2 - **0900 - 1000:** - Doors open. Coffee and breakfast available - **1000 - 1040:** - [EIP-7745](https://eips.ethereum.org/EIPS/eip-7745) Presentation and Discussion - Zsolt Felfoldi - **1030 - 1100:** - DiscV5 Discussion - **1100 - 1200:** - Morning Coworking & Open Discussion space - **1200 - 1300:** - Lunch - **1300 - 1600:** - Afternoon Coworking
Last changed by  
 
Piper Merriam
352

Read more

Portal Network and Protocol Guild

Portal Network is included in protocol guild under the "Research and implementation experiments related to potential protocol changes" provision. There are currently three teams included in PG under Portal. Trin - 7 Members Fluffy - 2 Members Ultralight - 1-2 Members (Note they also work on EthereumJS) At present, there are two Portal network clients who are not part of PG Shisui - ?3? Members Samba - 1-2 Members

2/12/2025
Portal Team Work on 4444s

This document is intended to be a rough collection of the work that the Portal team has done to advance EIP-4444 implementations in execution clients. This also documents the work we've done to encourage adoption of Portal network by execution clients. Worth noting that 4444s and Portal adoption are not the same thing and we've worked to keep them separate. We believe that Portal is the best solution, but we also recognize that to be effective facilitators of the 4444s discussion, we can't intrinsicly link Portal and 4444s as the same thing. In this document, we start the timeline in May of 2024. If anyone wants to dig back further in time, I'm happy to go on that journey with them. A bit of "meta" In this section I have made some assumptions about other peoples perspectives. I'm very open to corrections here. My goal isn't to put words in other people's mouths, but rather to put some words down so that we can refine them if needed to get a clear understanding of the situation. Please please please provide me with corrections if I've gotten some of this wrong which I'm sure I have -Piper

1/13/2025
Analysis of bumping eth protocol version

This document is the successor to this document Goal of this document is to outline the client behaviors and consequences related to bumping or NOT bumping the eth protocol version with respect to 4444s and serving pre-merge data. Cases to Consider We will try to enumerate the following cases. Clients that do not update and remain on old client versions Clients that do update Clients that drop the pre-merge data

12/19/2024
Execution Client 4444s Rollout Plan

Goals: Determine whether the rollout of 4444s should bump the eth protocol version or not. TLDR: We should probably bump the eth protocol version. Is the bump required? Short answer is "No" The actual message payloads to the eth protocol do not change, and so the the bump is purely anchored to client behavior. Exploring client behavior

12/9/2024
Read more from Piper Merriam
Published on HackMD