-
Notifications
You must be signed in to change notification settings - Fork 243
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
support multiple consensus nodes in nimbus-vc #1988
Conversation
This is already supported by Do you see a significant UX improvement by parsing comma-separated for the user, instead? |
IMO it is nice to set it up in the same way in the .env for different validator clients. |
To elaborate, personally I had used Teku VC before w eth-docker, so I was accustomed to putting the comma separated list of nodes in CL_NODE. I made this PR because I got an error when I tried to do the same while setting up a new Nimbus VC node. I didn't notice the adjacent comment in the .env file about Nimbus to be honest. At the same time though, without seeing the underlying technical reason for why Nimbus VC is setup differently currently (ie the slight difference in how the endpoints are passed to the VCs), naively I don't think the eth-docker user would have reason to expect there to be different ways of doing the same thing between different clients |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good. One style change please: Could you make it __nodes
and __node
please. I am trying to switch to a style where UPPERCASE
is something external to the script, like a var in .env
, and __lowercase
is a variable local to the script
BTW linting: Check out |
done c3aadd5 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for this!
pass CL_NODE into docker-entrypoint-vc.sh script, parse in script giving ability to pass multiple '--beacon-node=http://blah:5052' to the validator client via comma separated .env CL_NODE in the same way that you can with other validator clients
(refer to https://nimbus.guide/validator-client-options.html)