P2P2026-09-09_008

P2P Networking #008

2026-09-09 3 decisions 939 transcript lines

Transcript

At a glance

EIP-8411 (fast payload broadcast / execution payload segmentation) submitted for PFI for Hegota; to be discussed at ACDC the following day
Hegota tentatively Q3/Q4 2027 (~15 months out); EIP-8411 targeting PFI at that forkverify date
ETHP2P broadcast integration into Prysm: DevNet testing imminent on Glamsterdam payload broadcast

Detailed notes

Client Updates

  • •Prysm: partial columns PR for Gloas fully reviewed/tested, awaiting one upstream PR before merge to release branch00:06:30
  • •Prysm: peer scoring overhaul dev-complete; tested on Hoodi for one week, no regressions; adds per-agent observability and pruning metrics00:07:11
  • •Lighthouse: fixing incorrectly ordered fields in partial messages; Gloas column gossip limit replacing static 8MB cap with dynamic limit based on blob schedule max00:09:52
  • •Nethermind: sparse blob pool in master; working on IPv6 support, near completion00:14:00

Ethp2p Progress

  • •Raúl implementing shared QUIC transport for Prysm: single endpoint serves both LibP2P and ETHP2P streams; stream routing via ALPN negotiation + first-byte slash detection; backwards-compatible with LibP2P-only peers01:26:38
  • •ETHP2P payload broadcast branch hooked into Glamsterdam in Prysm; ready for DevNet testing01:44:35
  • •Raúl previewed unified Ethereum networking specs site aggregating consensus-specs, EIPs, and ETHP2P/Waggle specs in one taxonomy; unreleased, targeting this week01:45:19
  • •ETHP2P advantages over LibP2P: unidirectional streams, datagrams, zero-RTT, session resumption, per-chunk stream interruption, slot-scoped cache lifetimes; lambdaclass has WIP Rust implementation01:51:06

Rowdas Proposal

  • •RowDAS adds row-based reconstruction duties to PeerDAS: vertical (distributed CPU across supernodes) and horizontal (supernodeless fallback) reconstruction00:15:44
  • •Each supernode assigned a row duty (no custody requirement); duty-sharded variant skips row topics entirely, using only column topics — simpler first-stage option00:19:38
  • •KZG reconstruction per blob ~162ms single-core; RowDAS reduces per-node CPU ~2 orders of magnitude; degrades to PeerDAS levels under adversarial conditions00:22:51
  • •Implemented on Csaba's Prysm branch (on top of partial messages); row-based reconstruction without supernodes confirmed working at 65+ nodes00:23:52

Eip Proposals Hegota

  • •EIP-8411 (fast payload broadcast): replaces execution-payload topic with execution-payload-chunks; 64 segments, Merkle inclusion proof per chunk, payload-chunks-root added to bid; no erasure coding in v1 for simplicity01:14:44
  • •EIP-8411 requires consensus change (bid field extension); without it, mixed-mode operation is possible but increases attack surface and buffering burden01:16:00

Fast Payload Broadcast

  • •1MB payload over 50 Mbit uplink nodes (min-spec): current gossip-sub delivers last node in ~5s; all segmentation variants (A/B/C) converge near ~1s00:47:11
  • •Variant A (normal gossip-sub + 32KB segments): 1.7s → 1.0s with batch publishing → further gains with phase-aware forwarding and disciplined pull (one requester per segment)00:50:13
  • •Merkle commitment in the bid required to authenticate segments without full block; enables immediate per-segment forwarding upon receipt of signed beacon block00:52:09
  • •ETHP2P broadcast already implements chunking, push→pull phase transition, and pluggable nil encoder; Raúl offers to onboard collaborators and align with Csaba's work01:03:02

Action items

  • •Csaba to document partial-messages changes one-by-one for cross-team review and Waggle/ETHP2P alignmentCsaba
  • •Csaba and Raúl to align benchmarks and share code between simulation frameworks (Plisma vs ETHP2P)Csaba, Raúl Kripalani
  • •Kamil to extend EIP-8411 with chunk-before-bid handling rules and payload-chunks-root fieldKamil Salakhiev

Agenda

From the call issue #2214Show

Key decisions

  • EIP-8411 (fast payload broadcast / execution payload segmentation) submitted for PFI for Hegota; to be discussed at ACDC the following day

    PFIEIP-8411 was submitted for Proposed for Inclusion (PFI) status for the Hegota fork, with further discussion scheduled for the following ACDC meeting.
  • ETHP2P broadcast integration into Prysm: DevNet testing imminent on Glamsterdam payload broadcast

    GlamsterdamETHP2P payload broadcast integration is ready for testing on the Glamsterdam DevNet.
  • Hegota tentatively Q3/Q4 2027 (~15 months out); EIP-8411 targeting PFI at that fork

    The Hegota upgrade is tentatively scheduled for late 2027, with EIP-8411 as a primary candidate for inclusion.

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.