Lodestar Standup 2024-21 (June 4, 2024)

[philknows]

Meeting Info

June 4, 2024, 14:00-15:00 UTC
Zoom: shared on #lodestar-general ChainSafe Discord channel at 14:00 UTC

Agenda

• Planning Items
  • v1.19.0-rc.0 review
  • Presentation: refactor: improve types package to use forks as generics #6825
• Team Updates
• Open Discussion/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]

Presentation: #6825

any chance to have this in a separate meeting? won't be able to join tomorrow

[philknows]

@wemeetagain Sounds like discussing #6825 might be important for everyone to be available to participate and ask questions. What do you think? Here's some alternative dates if we're able to move it:

• Wednesday June 5 @ 1200 UTC (8am Eastern Time)
• Wednesday June 5 @ 1300 UTC (9am Eastern Time)
• Thursday June 6 @ 1200 UTC (8am Eastern Time)
• Thursday June 6 @ 1300 UTC (9am Eastern Time)

My preference would be one of the 1200 UTC times so it isn't so late for @twoeths .

[philknows]

Spoke to @wemeetagain. No worries if you cannot make the presentation tomorrow. There will be time to watch the recording, provide feedback and ask questions async in the essence of not having to schedule an additional sync meeting this week. #6825 will need more time for feedback anyway.

[philknows]

Also adding monthly PR scrub, so please come to the meeting with details on the status of your PRs.

[nflaig]

#6323 has been open for a while, we should consider a feature like that. There are a few interesting use cases like quickly spinning up a node on any network to test something even if you don't have a synced EL. Also good for people to run Lodestar in their dev environment to test proofs, light client etc. Ofc we shouldn't advocate for stakers but other than that I don't see a downside with this.

Also interesting use case of your EL needs to resync, you can produce (optimistic) attestations, and even still propose blocks with external builder. Of course no ideal, but better than being offline.

[nflaig]

Not sure about #6479, there has been no activity for a while. I can pick this up as it should be quite easy to get this to a mergeable state.

Might wanna ping the author, or otherwise close the PR for now

[philknows]

Specifically these PRs which have been opened for a while now without much discussion:

• electra branch: chore: rename caches and related functions to indicate finalized #6528

• External contributor: fix: make multiple api errors spec compliant #6479

• feat: add historical state regen #6033

• feat: use snappy-wasm #6483

• feat: add proposer boost reorg flag #6652

• feat: added release page in docs #6669

• feat: generalize blobs to data for extension ready for ils and/or data columns #6693

• chore: improve vitest output #6786

• chore: add new FAQ about yarn version #6796

• feat: enable debug apis by default #6824

• perf(reqresp): improve the reqresp request/response methods #6801

[jeluard]

Let's decide on #6550 and how installation fits into this.

[twoeths]

it took a lot of time to investigate performance issue in v1.19.0-rc.0 while beta is not used most of the time. How about we deploy some checkpoint commits every week so that we can trace which PRs cause issues at release time? this is important for issues with docker deployment since most of PRs are tested with service deployment

[philknows]

Closing for #6855