<aside> ☝ Data Availability Sampling (DAS) is a key primitive to scaling blob space for L2s on Ethereum. The first step is PeerDAS – scheduled to ship in the Fusaka hard fork. The focus of this site for now is on PeerDAS, but will expand over time.
</aside>
key links:
contributor list →
roadmap doc →
PM.md (updating soon)→
Meeting Minutes →
Key Takeaways and Action Items Highlighted below
| Team | Team Roadmap | Call #22 Updates |
|---|---|---|
| Prysm | link | • Worked on redesigning the database to fix issues with data column storage |
◦ Successfully synced a node on the peerdas-devnet-5 from a local computer
• Added missing unit tests for PeerDAS
• Worked w/ Francis from Base worked on getBlobV2 and equivalent API when proposing a block |
| Lighthouse | link | • Still addressing sync issues
◦ Improving scoring during sync to enhance abilities to sync to head
◦ DevNet 5 node (Lighthouse G2) is still down, but root cause identified
◦ Fixes pending review before merging to main branch
• Created spec PR for distributed publishing (see below)
• Working on making Lighthouse compliant with the spec
◦ Current full node doesn't do distributed publishing
◦ This affects blob propagation |
| Teku | link | • Released validator custody, started testing with DevOps
• Added new PeerDAS metrics with help from Katya (see below)
• Working to resolve various bugs |
| Lodestar | link | • Made progress with refactoring and unit testing
• Onboarding a new contributor to help with validator custody
• Addressing peer management issues to ensure there are peers listening to all subnets
• Looking at improving how peers connect to those listening to correct topics |
| Nimbus | - | - |
| Team | Team Roadmap | Call #22 Updates |
|---|---|---|
| Geth | - | • Open pull request about encoding, limited progress due to vacation schedules |
| Nethermind | - | • Has proof of concept branch with API methods implemented, ready to join DevNet as execution layer client |
| Reth | - | • All types implemented, waiting for specs to be locked in, 1-2 days from being ready |
| Besu | - | |
| Erigon | - |
| Team | Link | Discussion (key points highlighted) |
|---|---|---|
| ethPandaOps | link | peerdas-devnet-5 status: |
| • Gradually increasing malicious peers (withholding columns or delaying publication) | ||
| • Currently ~30% of network acting malicious | ||
| • Network composition: 60% full nodes, 40% super nodes | ||
| • Waiting for Prism fix to be deployed before increasing malicious nodes further | ||
| ethPandaOps | link | peerdas-devnet-6 status: |
| • Target timeline: approximately two weeks |
• Validator custody not required for initial launch but is a priority. • Client teams should focus on self-proof computation first, then validator custody • Validator custody can be deployed later as it's backward compatible | | ethPandaOps | | Testing Tools Updates: • Spammoor: tx format for tx submitter does not change, so no change required • P2p tester: Sam is still working on its - won’t be ready in the next few weeks • Checkpointz: waiting for spec to finalise. For now its possible to checkpoint sync via beacon nodes | | Sunnyside | link | Max Blobs Testing: • Tried different CL client combinations, see above link for more details • Some EL clients are hitting some tx pool limits • Will publish another report in a couple of hours after the call | | Sunnyside | link | Updated Report (post-Meeting) |