Skip to content

Lodestar Weekly Standups 2025

Phil Ngo edited this page Jan 15, 2025 · 3 revisions

The Lodestar team hosts planning/standup meetings weekly on Tuesdays at 3:00pm Universal Standard Time. These meetings allow the team to conduct release planning, prioritise tasks, sync on current issues, implementations and provide status updates on the Lodestar roadmap.

Note that these notes are transcribed and summarized by AI language models and may not accurately reflect the context discussed.


Lodestar Standup 2025-02 (January 14, 2025)

Agenda: https://github.com/ChainSafe/lodestar/discussions/7337

Planning/Discussions

Release Planning

  • Metrics review for 1.25 release showed no concerning issues. Release planned for later today.
  • Next RC due date discussed for 1.26:
    • Agreed to cut RC on January 24th, aiming for release on January 31st
    • Acknowledged shorter timeframe but aligns with goal of more frequent releases

Major PRs and Features

  • Plans include merging work to switch to Snappy Wasm for decompression once it is rebased and redeployed.
  • They also want to revisit the libp2p 2.0 and GossipSub updates, testing them separately from the “IDONTWANT” feature to address prior latency issues.
  • SIMD support for SSZ was merged and tested, aiming for inclusion in 1.26
  • Continued benchmarks for different JavaScript runtimes (e.g., Bun, Node) are underway to handle garbage collection impacts on benchmarking consistency

Devnet-5 Branch Cleanup and Integration to Unstable

The discussion around the Devnet-5 branch cleanup and integration plan back into unstable covered a few key points:

  • There is a need to clean up the DevNet-5 branch.
  • The branch contains changes that are not only related to Electra but also affect how forks are handled.
  • The DevNet-5 branch includes changes to the NEP (Network Upgrade Process), which requires caution during merging.
  • There are preset value updates in the minimal preset that affect CI and sim tests.
  • Current CI is failing due to the preset changes.
  • The team needs to wait for a Lighthouse image with updated presets to fix the CI issues.
  • As a temporary measure, they might consider running tests up to Deneb instead of Electra until the Lighthouse image is available.

Action Items

  • Review and fix any issues in the DevNet-5 branch before merging.
  • Wait for the Lighthouse image update to resolve CI problems.
  • Plan the integration carefully to avoid disrupting the main development flow.

The team emphasized the importance of not rushing the integration process and ensuring thorough testing before merging DevNet-5 changes into the unstable branch.

Electra Cleanup

  • Team to review and tag remaining Electra-related todos
  • Plan to integrate DevNet-5 changes into Unstable after 1.26 RC

Updates

Gajinder

  • Reviewed latest PeerDAS spec changes
  • Investigated TypeScript and Rust interop for potential light client snarkification

Nazar

  • Working on moving runtime setup to SSZ repo
  • Debugging benchmark issues related to garbage collection

Nico

  • Completed gas limit check PR
  • Finished remaining DevNet-5 tasks
  • Started looking into FOSSIL implementation

Matt

  • Finalized remaining work on the SSZ SIMD PR.
  • Focused on PeerDAS groups PR and a thorough review of the overall PeerDAS code.
  • Rebasing changes on Electra and merging updates for Fulu, aiming to test them in DevNet soon.

Cayman

  • Made PRs to discv5 for library improvements and removing costly crypto dependencies.
  • Reviewed the SSZ ZIG implementation and has a PR coming for enhancements.
  • Continues to review PRs such as Peer Discovery for subnet requests and related code[2].

Tuyen

  • Continued work on BLST binding for Zig and Bun testing signature, secret key, and public key classes.
  • Working on more advanced features like verifying multiple aggregate signatures.
  • Raised small PRs for PeerDAS improvements, including minimum subnet checks and batch download fixes.

NC

  • Focused on FOCIL implementation, estimated to be halfway complete.
  • Contributing to the Beacon API aspects for FOCIL and coordinating on design discussions in the open spec documents.

Phil

  • Upcoming call with Alex Stokes and Peter for quarterly feedback
  • Coordinating team attendance for upcoming interops

Andrew

  • Followed up on RPC endpoints discussion with infrastructure team
  • Reconnecting with operators for feedback, including questions on new release stability and validator effectiveness data

Peter

  • Highlighted an upcoming blog post draft for a new “Fabric” standard for rollups, aiming to unify L2 solutions without introducing new networks or tokens
  • Mentioned synergy with potential L2 API expansions in Lodestar and continuing research on universal rollup definitions

Lodestar Standup 2025-01 (January 7, 2025)

Agenda: https://github.com/ChainSafe/lodestar/discussions/7326

Planning/Discussions

Strict Cadence for Releases

  • Implement stricter cadence for releases to prevent performance regressions from large accumulations of unreleased commits.
  • Proposed cadence: Close door to PRs on specific day (Friday), cut RC, deploy to beta group, review metrics and release after standup the following week.
  • Goal is to avoid situations like the recent accumulation of 97 PRs.

Lodestar 1.25 Planning and PR Grooming

FOCIL and PeerDAS

  • FOCIL project gaining momentum; need to assign lead and break down spec for implementation.
    • NC and Nico will take charge on this implementation
  • Spec itself is small. Changes to beacon node, validator, P2P and fork choice. Due for next breakout call January 15.
  • PeerDAS is high priority; need to get it working to avoid max blob count issues. Continue implementation and testing.
    • Matt and Gajinder will take charge on this implementation. Tuyen in support role.
    • Kurtosis configs and interop testing scheduled for two weeks from now.

Pectra Devnet-5

  • Local testing via Kurtosis is ongoing, but no public spin-up yet.
  • Builder flow will start being tested.
  • Focus on fixing bugs and ensuring stability before public release.

Updates

BlockOps Role

  • Closing role, shifting BlockOps role back towards software engineering focus.

Zig Implementation of DiscV5

  • Cayman:
    • Completed ENR encoding, decoding, signing, and verifying implementation in Zig.
    • Will share work and findings with team soon.

Zig BLS Library

  • Tuyen:
    • Making progress on getting Zig BLS library operational.
    • Expects to have good news to share next week.