P2P2026-10-07_009

P2P Networking #009

2026-10-07 1 decision 752 transcript lines

Transcript

At a glance

Lighthouse will implement EIP-8411 regardless of Hegota fork inclusion, with network backward compatibility
Decoupled consensus 500-node Cloud Run simulation — October 08, 2026 (tomorrow)verify date

Detailed notes

Client Updates

  • •Lighthouse: simplifying networking stack; prototyping EIP-8411 and attestation bundling00:18:05
  • •Prysm: partial columns merged and enabled by default for Fulu and Gloas; peer scoring/connectivity revamp soaking on mainnet and Hoodi nodes; dashboard demo planned for next call00:19:10
  • •Lodestar: QUIC 1.3 in progress; partial columns not enabled until after Gloas mainnet00:21:01
  • •Geth (Csaba): published post on blob pool protections; hardening of sparse blob pools this cycle00:22:13

Service Discovery

  • •Felix (Geth): topic-based service discovery now in discv5 spec, replacing old unimplemented messages; allows targeted peer search without ENR encoding00:32:18
  • •Spec considered final; Geth implementation (with Datahop) in progress but not merged; incremental deployment supported — not all nodes need to upgrade simultaneously00:35:03
  • •Per-node index table is bounded (constant storage overhead); scales with network size; post-quantum ENR growth motivates moving away from full-network crawl assumption00:50:46

Eip Proposals Hegota

  • •EIP-8411 (segmented execution payload broadcast): CFI for Hegota; splits payload into 64 chunks; reduces propagation latency ~3×; includes consensus change adding chunk root to bid01:10:33
  • •Lodestar concern: insufficient mainnet data showing propagation problems; risk of scope creep delaying Hegota past June; prefer deferral to I-star if not clearly needed01:12:28
  • •Counter-arguments: testnets lack realistic builder/home-node/bandwidth conditions; machinery needed regardless for PQ signatures and LeanVM proofs; segmentation is a prerequisite unlock (consensus bid change) for future networking work01:13:51
  • •Lighthouse committed to implement EIP-8411 regardless of Hegota inclusion, with backward compatibility; Prysm expressed interest (thumbs up from Vlad/Gattaca)01:43:02

Gloas Sepolia Bandwidth Profile

  • •Post-Glamsterdam Sepolia bandwidth profile: execution payloads propagate immediately at slot start, not after attestation threshold00:24:00
  • •Lodestar (no partial columns): data column sidecar bandwidth ~10x higher than Prysm (e.g., ~1 MB vs ~120 KB per block)00:28:30
  • •Lodestar receiving up to 77 copies of execution payload per message (~150 KB × 61+); likely IDONTWANT bug fixed in recent release — version under investigation00:30:35

Dc Simulations Decoupled Consensus

  • •Sukun: Shadow sims (100 nodes, 20% supernodes) testing decoupled consensus with 8-slot rounds; 2,500 attesters/subnet vs. ~500 today; 500-node Cloud Run sim scheduled for tomorrow00:53:43
  • •Three strategies under simulation: (1) all FFG votes at slot start, (2) staggered per-second publishing, (3) three committees across slot; goldfish vote latency improves significantly in strategies 2 and 300:56:23
  • •Key problem: no cross-topic stream prioritization between goldfish and FFG meshes; QUIC stream priorities only work per-connection00:58:48
  • •Plan: integrate GossipSub IHAVE/IHAVEv1 tracer; also attempt to make X-ray work with Shadow simulations01:00:49

Action items

  • •Lodestar: verify IDONTWANT fix is present in Sepolia-targeted release; investigate 60-77 duplicate execution payload copies observedLodestar (Matthew Keil / cayman)
  • •Add X-ray support to Shadow simulator; raise PRSukun Tarachandani
  • •Raise EIP-8411 on upcoming ACDC call for broader client alignmentKamil Salakhiev

Agenda

From the call issue #2262Show

– Clients updates – Gloas Sepolia bandwidth profile – Service discovery by Felix – DC simulations by Sukun – 8411 discussions (tentatively)

Key decisions

  • Lighthouse will implement EIP-8411 regardless of Hegota fork inclusion, with network backward compatibility

    Lighthouse commits to implement the segmented execution payload broadcast (EIP-8411) irrespective of whether the Hegota fork is adopted, ensuring backward compatibility.

EIPs discussed

AI Disclaimer: Some content or metadata on EIPsInsight may be AI-inferred or automatically compiled. If you find any discrepancy, please contact us at dev@avarch.org.