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

support multiple consensus nodes in nimbus-vc #1988

Merged
merged 6 commits into from
Nov 18, 2024

Conversation

b0a7
Copy link
Contributor

@b0a7 b0a7 commented Nov 16, 2024

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)

@yorickdowne
Copy link
Contributor

This is already supported by VC_EXTRAS for Nimbus. .env documents this:
"For Nimbus VC client, put the first beacon node here, and use VC_EXTRAS for additional."

Do you see a significant UX improvement by parsing comma-separated for the user, instead?

@b0a7
Copy link
Contributor Author

b0a7 commented Nov 17, 2024

This is already supported by VC_EXTRAS for Nimbus. .env documents this: "For Nimbus VC client, put the first beacon node here, and use VC_EXTRAS for additional."

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.

@b0a7
Copy link
Contributor Author

b0a7 commented Nov 17, 2024

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

Copy link
Contributor

@yorickdowne yorickdowne left a 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

@yorickdowne
Copy link
Contributor

BTW linting: Check out CONTRIBUTING.md, we have a pre-commit hook that makes this so much easier to lint on local commit

@b0a7
Copy link
Contributor Author

b0a7 commented Nov 17, 2024

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

done c3aadd5
double checking, is test-lodestar the right label and not nimbus?

Copy link
Contributor

@yorickdowne yorickdowne left a 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!

@yorickdowne yorickdowne merged commit 743db20 into eth-educators:main Nov 18, 2024
25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants