P2P2026-05-20_001

P2P Networking #001

2026-05-20 1 decision 498 transcript lines

Transcript

At a glance

Lighthouse will enable partial columns on Hoodi by default while keeping it disabled on mainnet
June 2026 — Lighthouse partial columns release targeting Hoodi deployment

Detailed notes

Blob Pool

  • •GetBlobs V3 latency root cause suspected: MMAP/disk-paged values in Billy store (Geth); CPU profile needed to confirm00:15:03
  • •Sparse blob pool: bitmap endianness ambiguity caused Nethermind and P2P implementation bugs; spec clarification PR merged00:23:37

Client Updates

  • •Lighthouse: Gloas partial column support nearly complete; pending review00:11:47
  • •Lighthouse plans to enable partial columns on Hoodi by default (mainnet off); release targeting June00:33:10
  • •discv5: Besu lacks parallel stack support; Nethermind has it disabled on mainnet; Reth uses wrong port00:27:30

Networking Research

  • •Raúl presented batched/pre-aggregating attestations at source proposal (EIP PR #11589) targeting Hegota00:37:46
  • •Key mechanism: two-way seal binding prevents permutation attacks; eliminates need for new slashing conditions00:44:14
  • •Worst-case spam bounded: each validator can act as batcher only once per committee per slot00:51:23
  • •Post-quantum concern raised: BLS-specific benefits may not carry over; physical consolidation still needed long-term01:00:27

Action items

  • •Run CPU profile on Geth node during devnet load test to diagnose GetBlobs latencyMarco Munizaga / EthPandaOps
  • •Review batched attestations EIP PR #11589; cryptographers specifically requested to evaluateGottfried Herold / crypto team

Agenda

From the call issue #2051Show

– Cell-level deltas ( @MarcoPolo ) – Sparse blobpool ( @healthykim, @kamilsa ) – Ethp2p updates ( @raulk )

Key decisions

  • Lighthouse will enable partial columns on Hoodi by default while keeping it disabled on mainnet

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.