Write genesis into config file when init network #2059
Closed
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.
Description
Write genesis into config file when init network
Rationale
when we use the cmd
init-network
to set up a clustergenesis will not be written into config.toml any more from #1839
it indeed make the
config.toml
file much more succinct,but we could not configure hardfork blocks or times in
config.toml
any morewe don't always can set hardforks in genesis.json, for example:
a cluster have set hertz hardfork is running, then new version of bsc including shanghai hardfork released.
then the cluster may need to upgrade to the latest version and enable shanghai
the only way is to configure shanghaiTime in the
config.toml
Example
add an example CLI or API response...
Changes
Notable changes: