We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
network can be read from the config.toml file, seems no need to add this extra flag.
NA
The text was updated successfully, but these errors were encountered:
Rationale network can be read from the config.toml file, seems no need to add this extra flag. Implementation NA
some commands not support using config.toml such as importHistory
importHistory
other few scenarios, some actions happened before reading config.toml such as func prepare(ctx *cli.Context)
func prepare(ctx *cli.Context)
and in addition, '--chapel' is totally following the geth
NetworkIdFlag = &cli.Uint64Flag{ Name: "networkid", Usage: "Explicitly set network id (integer)(For testnets: use --goerli, --sepolia, --holesky instead)", Value: ethconfig.Defaults.NetworkId, Category: flags.EthCategory, }
I think we can support removing '--chapel' and read the networkId from config.toml when we do a sync, but not removing --chapel totally.
--chapel
Sorry, something went wrong.
buddh0
No branches or pull requests
Rationale
network can be read from the config.toml file, seems no need to add this extra flag.
Implementation
NA
The text was updated successfully, but these errors were encountered: