Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PeerDAS Breakout Room | Call #22 | March 25, 2025 #1401

Closed
will-corcoran opened this issue Mar 23, 2025 · 3 comments
Closed

PeerDAS Breakout Room | Call #22 | March 25, 2025 #1401

will-corcoran opened this issue Mar 23, 2025 · 3 comments
Labels
Breakout Type: Topic-specific breakout calls DA Topic: Data availability PeerDAS Series: PeerDAS

Comments

@will-corcoran
Copy link

will-corcoran commented Mar 23, 2025

PeerDAS Breakout Room | Call 22 | March 25, 2025

Date/Time: Mar 25 (Tues), 2025, 10:00 UTC
Duration: 60 minutes
Zoom link
Ethereum Protocol Call calendar
Notes
Previous call

Agenda

  1. Client updates

    • Feature Completeness
      • Validator Custody
      • Distributed Blob Publishing
      • Move Cell Proof Computation to Tx Sender
        • implemented by one EL client req'd for devnet-6
      • getBlobsV2 Implementation
    • Cell Proof PoC by Francis
    • Source of Truth link (please review below, validate or provide)
  2. Devnet updates

  3. Spec discussion

    • See below for EIP and Spec-related questions
  4. Open discussion

    • TEMP CHECK: Ship peerdas-devnet-6, be feature-complete (PeerDAS* and EOF) and ship fusaka-devnet-0 by June 1.

*Distributed Blob Publishing and E.L. Cell Proof Computation

Agenda Supplements

PeerDAS Roadmap GoogleDoc

Client-related Items

Having a single 'source of truth' for others to track your progress on PeerDAS-related implementation would be quite helpful. If you could either provide a link (if one is not listed below for your team) or validate the link (if one is shown) for your team prior to Call 23, that would be great.

CL Team PeerDAS Progress Sources of Truth

Team Source of Truth Active Contributors
Prysm TODO Manu, Niran
Lighthouse TODO Jimmy, Pawan, Dapplion, ethDreamer
Teku TODO Dmitrii
Nimbus - Agnish
Lodestar TODO Matthew Keil, Katya, g11tech, Derek G

EL Team PeerDAS Progress Sources of Truth

Team Source of Truth Active Contributors
Geth - Marius, Lightclient
Nethermind - ??
Reth - ??
Besu - ??
Erigon - ??

Others (not exhaustive, just for reference)

Team / Org Active Contributors Key Responsibilities
Base Francis, Hugh C research and implementation
Sunnyside Labs Mininny, J, Taem, Tei Max Blobs Analysis & Data Collection
ethPandaOps Pari / Barnabas Devnet coordination & testing
ethPandaOps Sam / Matty / Andrew Data collection & analysis
ethPandaOps pk910 / Rafael Tooling
EFR - Consensus R&D Francesco Validator Custody Spec
EFR - Protocol Security Justin Traglia Consensus Spec
EFR - Research Ops Will Coordinator

Testing Items

Tooling Updates

Team Item Discussion Topic
ethPandaOps Spamoor & tx spammer Status on new tx format implementation?
ethPandaOps p2p testing tool Progress on tool for client <> RPC reliability testing?
ethPandaOps checkpointz Update on implementation for devnet-6?
Sunnyside Labs & Sam Root Cause Analysis Status on investigation of 10-blob performance failure?
Sunnyside Labs & Sam Random Configuration Testing Progress on network failure analysis?

Misc Testing Discussion Items

Category Item Discussion Topic
Testing Configuration Deploy at least one node with "withhold column" flag for testing Status?
Testing Configuration Verify all nodes are properly configured as full nodes Status?
Testing Configuration Pre-mine node keys to ensure coverage across all column subnets Status?
Testing Configuration Implement flag to advertise false CGC count (to trick other nodes into thinking the false flag belongs to a supernode, but not serve RPC requests) Status?
Networking Address inode limitation issue for Prysm (currently working on fix to include all subnets in one file) Status?
Networking Consider implementing batch publishing columns optimization Status?

Spec-related Items

Item Status / Discussion Items
EIP-7594 PeerDAS, championed by Francesco
Appears to be comment free and ready to merge - any updates on the status of this EIP?
EIP-7892 (draft) BPO Harkforks, drafted by ethDreamer
What is the current status of this? Considered for Inclusion in Fusaka?
EIP-7870 (draft) Hardware and Bandwidth Recommendation for Validators and Full Nodes, Pari(?)
Discuss: potential impact on PeerDAS & likelihood of being SFI for Fusaka.
EIP-7872 (draft) Max Blob Flag for Local Builders, Francesco(?)
Discuss: potential impact on PeerDAS & likelihood of being SFI for Fusaka.
Type Item Contributor Status / Discussion Items
consensus Basic Validator Custody Francesco Done, confirm
consensus make validator custody static for beacon node run session g11tech Ready for review - minor, open comment
consensus Complete validator custody specs GabrielAstieres Pending review from Stokes
consensus Add note about using getBlobs with DataColumnSidecar in Fulu Justin Traglia Open issue, discuss
consensus Add Distributed Blob Publishing to Fulu networking spec Jimmy New (s/o Jimmy) appears to be ready to merge, discuss
consensus Update BlobsBundle for Fulu Justin Traglia Working through some comments with g11tech
execution Update the type for blob_gas_used Shashwat-Nautiyal Working through some comments with Guru
execution tests feat(tests): peerdas tracking issue dancertopz Tracking issue for the required testing coverage for the EL for PeerDAS
builder Add EIP-7594 (PeerDAS) related changes Francis New (s/o Francis) - cell proof-related - appears to be ready to merge
execution api Add EIP-7594 (PeerDAS) related changes Francis Updated (s/o Francis) - cell proof-related - appears to be ready to merge
beacon api Add EIP-7594 (PeerDAS) related changes Francis New (s/o Francis) - cell proof-related - appears to be ready to merge
beacon metrics PeerDAS metrics: add data column, kzg, custody metrics Katya Appears to be being maintained as needed

Old Issues (consensus spec)

Please review this list and close any old issues that are no longer active.

@github-actions github-actions bot added Breakout Type: Topic-specific breakout calls DA Topic: Data availability PeerDAS Series: PeerDAS labels Mar 23, 2025
@ethDreamer
Copy link

Wanted to talk about adding BPO forks to fusaka:

@KatyaRyazantseva
Copy link

Agenda Supplements

PeerDAS Roadmap GoogleDoc

Client-related Items

Having a single 'source of truth' for others to track your progress on PeerDAS-related implementation would be quite helpful. If you could either provide a link (if one is not listed below for your team) or validate the link (if one is shown) for your team prior to Call 23, that would be great.

CL Team PeerDAS Progress Sources of Truth

Great summary! May we have it updated on a regular basis somewhere here for example?

@will-corcoran
Copy link
Author

Thanks Katya!

Yep, I am hoping to get that part of the PM document updated this weekend. :)

Great summary! May we have it updated on a regular basis somewhere here for example?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Breakout Type: Topic-specific breakout calls DA Topic: Data availability PeerDAS Series: PeerDAS
Projects
None yet
Development

No branches or pull requests

3 participants