Closed michaelneuder closed 6 months ago
I'd love to spend some time discussing gossip IL and blocks as separate objects or not. Although we've agreed to pursue the minimal viable approach for this POC by gossiping "together" and avoiding extensive debates, if we are 80% certain about preferring to gossip separately, it seems more logical to design this POC around separate subnets to prevent wasted effort.
Let's start by listing some pros and cons to initiate the discussion.
Improved Pipelining The period between seconds 2 and 4 is considered the busiest and most critical for a node to verify, process a block, and determine the head. We should avoid any additional processing during this time at all costs. Separating IL enables a proposer to broadcast IL at the 11-second mark of the previous slot, allowing for the processing of IL between seconds 0-1 or 0-2, and possibly even 10-12 in the previous slot.
Lighter Block A block without IL will be lighter to handle, resulting in less bandwidth spikes and faster dissemination across the p2p network.
No Beacon Block Gossip Changes If the beacon block gossips together with IL, we would need to modify the block gossip validation steps or even libp2p to accommodate scenarios where the same block could have multiple ILs for different peers. This introduces unnecessary complexity.
No Builder API Changes If the beacon block gossips together with IL, validators would need to send the IL to the relayer either during the getHeader or getPayload phase. This adds complexity, and ideally, we want the relayer to have fewer tasks, not more.
Reasons for gossiping together:
happy monday! tentative agenda; please feel free to add / modify!
agenda - 3/18
Meeting Info
March 18, 2024, 14:00-15:00 UTC Ethereum Protocol Calls Calendar subscription Stream: https://youtube.com/live/GVdkDXZTtnw Zoom: https://ethereumfoundation.zoom.us/j/86546873900?pwd=vKeh53OaWLyDLqgVJKfjZQdzrzoSbt.1
Agenda
Related links