Fix: Broken Lido DV Exit and Lido validator ejector when a secondery CL client is added to Charon
#1950
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yorickdowne
requested changes
Oct 4, 2024
… and LIDO_DV_EXIT_VERSION to environment migration; Bump environment version to 18;
yorickdowne
requested changes
Oct 6, 2024
Co-authored-by: yorickdowne <[email protected]>
yorickdowne
approved these changes
Oct 6, 2024
|
Congrats, your important contribution to this open-source project has earned you a GitPOAP! GitPOAP: 2024 eth-docker Contributor: Head to gitpoap.io & connect your GitHub account to mint! Learn more about GitPOAPs here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding a secondary CL node endpoint to the
OBOL_CL_NODEvariable breaks thevalidator-ejectorandlido-dv-exitservices because they don't support fallback endpoints.This PR introduces an additional environment variable
OBOL_CHARON_CL_ENDPOINTSspecific to theCharonservice, which should be used to set the CL client for theCharonservice. Multiple endpoints can be separated by commas.