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 Quickstart Future Roadmap #17

Open
5 tasks
philknows opened this issue Apr 26, 2023 · 0 comments
Open
5 tasks

Lodestar Quickstart Future Roadmap #17

philknows opened this issue Apr 26, 2023 · 0 comments

Comments

@philknows
Copy link
Member

Based on a discussion with Lodestar team members, it was made clearer that:

  • lodestar-quickstart should not be promoted as an onramp to simplify Ethereum staking UX for Lodestar
  • Rather, this repository is a tool for advanced users and/or the Lodestar team to bootstrap a Lodestar node with various EL clients for easier testing, debugging and troubleshooting
  • It could be used by operators which seek to have a very typical setup with no-fuss tinkering alongside any of the multiple Ethereum EL clients via Docker
  • It is mostly used by Lodestar contributors (but open sourced for advanced users) to easily quickstart a full Ethereum node using Lodestar

Lodestar Quickstart will not seek to implement a full suite of customized features often requested by stakers for stakers upon request. The maintenance of this repository will likely remain very limited and will only prioritize functionality required by the Lodestar team at our discretion. Features which aim to customize or extend these scripts are not our priority if it doesn't contribute to our goals defined above. We will likely implement simple, progressive completeness and easy demo of capabilities quickly.

This issue tracks some features that we would like to implement for the scripts in this repository:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
@philknows and others