You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Add auto-pruning args for EL clients in a typical setup
GUI: Simplistic interface for customizing unique configs for each instance (e.g. feeRecipient, jwtToken, flags, etc.)
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 LodestarLodestar 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:
The text was updated successfully, but these errors were encountered: