Add flags for 3.0 testing#117
Merged
Merged
Conversation
pmaslana
approved these changes
Feb 3, 2026
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.
Note
Low Risk
Limited to CLI/network-constants generation and gated behind optional flags; main risk is producing incorrect testnet configs if values are mis-specified.
Overview
network generatenow supports additional optional inputs to populate 3.0/hard fork 2-related fields in the generatedNetworkConstants(hard fork 2 height, plot filter v2 zero-bit requirement, plot v1 phase-out epoch bits, and up to three plot filter v2 adjustment heights).The command adds corresponding Cobra flags and Viper bindings, and only sets these constants when the flags are explicitly provided (preserving prior output by default).
Written by Cursor Bugbot for commit 34db0e6. This will update automatically on new commits. Configure here.