Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lodestar v2.0 Roadmap #7011

Open
philknows opened this issue Aug 8, 2024 · 4 comments
Open

Lodestar v2.0 Roadmap #7011

philknows opened this issue Aug 8, 2024 · 4 comments
Labels
epic Issues used as milestones and tracking multiple issues.
Milestone

Comments

@philknows
Copy link
Member

philknows commented Aug 8, 2024

This issue is to compile milestones we would like to achieve to consider ourselves v2.0 ready. The general goal of major bumping Lodestar is to signify our client's ability to match and/or exceed metrics such as profitability/performance to a competitive degree.

*Subject to change, issue will be regularly updated to reflect new/modified milestones

Goals

Issues/PRs

Other Tasks

  • List deprecated CLI flags and remove
@philknows philknows added the epic Issues used as milestones and tracking multiple issues. label Aug 8, 2024
@philknows philknows added this to the v2.0.0 milestone Aug 8, 2024
@philknows philknows pinned this issue Aug 8, 2024
@twoeths
Copy link
Contributor

twoeths commented Aug 15, 2024

yes #7005 should be on v2 where we move to new database repositories, a node will not work without checkpoint sync url since we don't go with StateArchiveRepository anymore

@twoeths
Copy link
Contributor

twoeths commented Aug 23, 2024

the block arrival time is actually block time to head, our metrics are not the same to ProbeLab, created the issue in #7046

@philknows
Copy link
Member Author

Some other notes I found from previous discussions to potentially decide for adding to this milestone:

@twoeths
Copy link
Contributor

twoeths commented Oct 31, 2024

I think validator performance when subscribing to all subnets should be included in lodestar 2.0 roadmap too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
epic Issues used as milestones and tracking multiple issues.
Projects
None yet
Development

No branches or pull requests

2 participants