fix: add USE_BASE_CONSENSUS=true to .env.mainnet and .env.sepolia#1015
Open
fix: add USE_BASE_CONSENSUS=true to .env.mainnet and .env.sepolia#1015
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
2 participants
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 #1014
The .env file sets USE_BASE_CONSENSUS=true, but .env.mainnet and .env.sepolia were missing this variable entirely.
Since docker-compose.yml defaults to false, operators using NETWORK_ENV=.env.sepolia or .env.mainnet would silently fall back to op-node instead of base-consensus — missing the Base V1 upgrade on April 20th.
This adds USE_BASE_CONSENSUS=true to both env files to ensure base-consensus is used by default.