You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Waiting on PRs; implementing new transaction wrapper this week; working on getBlobsV2 and payload/blobs bundle changes. - Open PR: tx: add peerdas blob transactions support
Devnet / Testing Updates
PandaOps Updates
peerdas-devnet-6 is now live 🚀 (replacing peerdas-devnet-5 ☠️)
Treatment of BPO changes as hard forks with new fork hashes
CL Clients
Two options for CL BPO blob schedule config
Key questions:
Naming convention scalability
Parsing considerations for BPO*_{EPOCH,MAX_BLOBS} format
Parameter specification for error handling and ordering rules
Discussion Item 02 | Naming Convention Request
Request to rename the PRs with Add PeerDAS related changes titled prs to BeaconAPI: <the same thing repeated again>, in general Name of the repo/module: the peerDAS related changes happen within?
This helps keep the PRs more easily distinguishable as multiple items that need ot be tracked.
PeerDAS Breakout Room - Call 25 | April 15, 2025
Resources
Agenda Overview
A. Client Updates
B. Devnet / Testing Updates
C. Spec / EIP Discussion
D. Open Discussion
Agenda Details
Client Updates
CL Client Teams
EL Client Teams
- Open PR: tx: add peerdas blob transactions support
Devnet / Testing Updates
PandaOps Updates
peerdas-devnet-6
is now live 🚀 (replacingpeerdas-devnet-5
☠️)--throughput-increment-interval=600
Sunnyside Updates
Sunnyside Plan for This Week
getBlobs
getBlobs
optimizationsSpec / EIP Discussions
Open Specs & Discussions
Builder Spec Discussion
Draft Specs & Discussions
Discussion Item 01 | BPO Blob Schedule Config
EL Clients
CL Clients
Discussion Item 02 | Naming Convention Request
Request to rename the PRs with
Add PeerDAS related changes
titled prs toBeaconAPI: <the same thing repeated again>
, in generalName of the repo/module:
the peerDAS related changes happen within?Discussion Item 03 | Review High-Level Schedule
The text was updated successfully, but these errors were encountered: