Lodestar Standup 2024-4 (January 30, 2024)

[philknows]

Meeting Info

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

Agenda

• Planning Items
  • 1.15.1 hotfix release
• 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.

[wemeetagain]

Lets list and discuss areas where we've specialized individually, and how we can spread that knowledge thru the team.

[wemeetagain]

Lets discuss our strategy for management of open PRs.
Should we have draft PRs open that aren't close to review status -- that aren't ready for feedback?
Can we use issues to promote visibility of branches that don't need feedback?

[twoeths]

Just want to make sure we don't miss this, Nethermind has a metric to track notifyNewPayload time to reach execution engine, we should improve it. That should help improve attestation performance as well.
cc @g11tech @philknows

[twoeths]

also how to speed up EIP-6110 work of @ensi321

[ensi321]

Thanks @tuyennhv . Was about to say this.

Mainly want to discuss the EIP-6110 PR from several perspectives:

1. How to make it easier for review (Discussion session? Split it into smaller chunks?) especially when I will be away for two weeks and unavailable to answer questions in a timely manner. The original intent of this PR is to include everything controversial so everyone can discuss. There is a follow up PR planned for other things like renaming, refactoring etc.
2. How to manage it along with other Electra EIPs? Now that 6110 is scheduled for Electra, and @g11tech just created a new branch electra-fork feat: placeholder PR for electra #6352 . Should it first merge into the electra branch before unstable?

A further discussion that's nice to have is to establish the process of develop, manage and test the Electra EIPs.
eg. PR merge to electra-fork first then test or test at the time of the PR?

[g11tech]

yes, I will actively maintain and manage electra-fork and its participation into the devnets so you can consider me sort of the "fork-owner" as this kind of structure has served us well in past forks.

all the work for the fork will need to be build against and merged into the branch till we are running devnets on it.

then we can extract the work into the unstable.

[g11tech]

so as a first step, i will review and rebase 6110 work and get it merged ready into this

[g11tech]

(and please never do merge in your branch, always rebase as it really muddies the commit history and makes everything difficult)

[matthewkeil]

I added a discussion for how we handle skipped tests.

#6376

[nflaig]

If there is time left could quickly talk about what we should do with the env vars issue on k8s

• Handling environment variables prefixed with LODESTAR #6045

[nflaig]

We discussed to add this to a known issues page in our docs

• Add known issues page to docs #6378

[jeluard]

I would be interested in discussing the high-level strategy for 2024.

[philknows]

Very high level, but can give a brief summary on what was discussed during our last team retreat:

Priority 1: Adoption and Legitimacy
Priority 2: Research and Development
Priority 3: Improve Developer Experience
Priority 4: Performance Improvements
Priority 5: Improve User Experience

[philknows]

Closed in favour of #6390