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 #16 #1259

Open
jimmygchen opened this issue Jan 22, 2025 · 4 comments
Open

PeerDAS Breakout Room #16 #1259

jimmygchen opened this issue Jan 22, 2025 · 4 comments
Labels
Breakout Type: Topic-specific breakout calls DA Topic: Data availability PeerDAS Series: PeerDAS

Comments

@jimmygchen
Copy link

Agenda

  • client updates
  • peerdas-devnet-4
  • spec discussion
  • open discussion
@abcoathup
Copy link

@parithosh
Copy link
Member

I'd like to bring up the topic of moving the call to eth-o-clock in the future to align with other breakout rooms. The day can stay the same if there's no conflict with the protocol call calendar. Additionally, should we consider increasing the frequency as peerDAS might get more limelight?

@jimmygchen
Copy link
Author

I'd like to discuss:

  • Schedule for peerdas-devnet-4 launch
  • What are the state of KZG libraries? Have both c-kzg and rust-eth-kzg been audited and production-ready? Is the longer term plan to maintain both libraries?

Spec discussion:

  • What outstanding work remains on the PeerDAS spec?
    • Validator custody: nodes are required to download all additional columns within the DA window when their CGC increases, do we need to explicitly spec this out?
    • Distributed blob building: do we need any form of this in PeerDAS? if so, what are the minimum requirements?
    • DAS parameters for production: do we need further research in this area? e.g. is 128 column subnets what we should aim for? This may require increasing peer counts in some clients.

@jimmygchen
Copy link
Author

Thanks for everyone who joined the breakout call today!

Summary:

  • All clients have made good progress and are mostly devnet-4 ready πŸŽ‰
  • peerdas-devnet-4 will be launched shortly πŸš€
  • Teams started discussing peerdas-devnet-5 scope and ways to test distributed blob building.
  • There were some discussions to add more details to validator custodty and distributed blob building in the consensus spec.
  • Pari will start a poll on moving this call to a 3pm UTC from the next call, and change this breakout call to weekly!

More details in meeting notes here: https://docs.google.com/document/d/1Ng2IrCe28kTt1BnIsjtMlKHq2MHgaja24LhFXSvqfJQ/edit?usp=sharing

@nixorokish nixorokish added Breakout Type: Topic-specific breakout calls PeerDAS Series: PeerDAS DA Topic: Data availability labels Feb 4, 2025
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

4 participants