Lodestar Standup 2025-34 (September 23, 2025)

[philknows]

Meeting Info

September 23, 2025, 15:00-16:00 UTC
Google Meet: https://meet.google.com/csm-usmi-zkt

Agenda

• Open Discussion
  • EPF updates
  • Fusaka Retrospective
  • Fusaka Updates
    • Devnet-5 updates
    • v1.35.0-rc.0 - Testnet ready Fusaka release
  • Bun Updates
    • Software reusability and Bun priorities
  • Lodestar Zig Updates
  • Initial Glamsterdam Discussions
• Team Updates
• Closing Remarks

Instructions

Please post here any topics to be added for Standup discussions. Examples of agenda items are issues, discussions, proposals which require feedback, consensus from the team and/or community members.

[nflaig]

We should discuss when we wanna cut rc.0 for Holesky and if there is any urgent items that need to be addressed before that. It is expected from all clients to have releases before ACD on Thursday.

[philknows]

Added a discussion about software reusability and Bun priorities. The conversation came about to further discuss:

• Building Goals
  • Product-first versus library-first
  • Which libraries are high impact enough to warrant extensive support for large class of consumers? (e.g. Zig libs vs. Bun bindings vs. others)
• Reiteration of objectives and discussion of priorities

From @wemeetagain :

• I think we should generally focus on our product and our own usecases first and foremost
• this is a shift from "building a collection open source libraries" to "building an open source product" thinking
• this is not a license for shitty design or short-termism, rather an acknowledgement that we have limited time and resources, and we need to be strategic with how we build
• To the extent we build libraries, they should be high impact, for us, directly interfacing with our existing usecases and vision and/or for a known large class of consumers we care about
• Imo, the foremost locations we can provide high-impact libraries in this roadmap is via zig, with pure zig libraries or bindings around a c-api (and maintaining a few core useful cross-js-env libraries (types/api/etc))
• For that reason, (and for the purposes of keeping proper separation of concerns), we should separate our zig libraries from our bun bindings
• I'm currently bearish on our bun-ffi layer being reusable or useful beyond our application, planning for reuse at this stage feels immature and not helpful towards making a good product
• Imo a strategy for making our zig code more reusable via javascript needs more thought (maybe using web assembly) but also only after we succeed in our primary objectives or not at the expense of our primary objectives

[philknows]

I also intend to assign people to the remaining fulu issues, especially if they need to be completed before mainnet.

[philknows]

Notes located here: https://github.com/ChainSafe/lodestar/wiki/Lodestar-Weekly-Standups-2025#lodestar-standup-2025-34-september-23-2025

Closing for #8467