P2P2026-05-20_001

P2P Networking #001

2026-05-20 1 decision 498 transcript lines

Transcript

Call summary

Targets
  • June 2026 — Lighthouse partial columns release targeting Hoodi deployment - 00:34:48
Decisions
  • Lighthouse will enable partial columns on Hoodi by default while keeping it disabled on mainnet - 00:34:09
Highlights
  • Blob Pool:
    • ·GetBlobs V3 latency root cause suspected: MMAP/disk-paged values in Billy store (Geth); CPU profile needed to confirm - 00:15:03
    • ·Sparse blob pool: bitmap endianness ambiguity caused Nethermind and P2P implementation bugs; spec clarification PR merged - 00:23:37
  • Client Updates:
    • ·Lighthouse: Gloas partial column support nearly complete; pending review - 00:11:47
    • ·Lighthouse plans to enable partial columns on Hoodi by default (mainnet off); release targeting June - 00:33:10
    • ·discv5: Besu lacks parallel stack support; Nethermind has it disabled on mainnet; Reth uses wrong port - 00:27:30
  • Networking Research:
    • ·Raúl presented batched/pre-aggregating attestations at source proposal (EIP PR #11589) targeting Hegota - 00:37:46
    • ·Key mechanism: two-way seal binding prevents permutation attacks; eliminates need for new slashing conditions - 00:44:14
    • ·Worst-case spam bounded: each validator can act as batcher only once per committee per slot - 00:51:23
    • ·Post-quantum concern raised: BLS-specific benefits may not carry over; physical consolidation still needed long-term - 01:00:27
Action Items
  • Marco Munizaga / EthPandaOps - Run CPU profile on Geth node during devnet load test to diagnose GetBlobs latency - 00:19:36
  • Gottfried Herold / crypto team - Review batched attestations EIP PR #11589; cryptographers specifically requested to evaluate - 01:06:11

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.