fix: add base-consensus binary to geth and nethermind Dockerfiles#1017
Open
fix: add base-consensus binary to geth and nethermind Dockerfiles#1017
Conversation
Collaborator
🟡 Heimdall Review Status
|
This file contains hidden or 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
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.
Fixes #1016
reth/Dockerfile already includes the base-consensus binary, but geth/Dockerfile and nethermind/Dockerfile were missing it entirely.
Operators using geth or nethermind with USE_BASE_CONSENSUS=true would get "Base client is not supported for this node type" error and fail to start — potentially missing the April 20th Base V1 Sepolia upgrade deadline.
Changes: