-
Notifications
You must be signed in to change notification settings - Fork 109
New issue
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
--customnetwork:FILE.json
does not work with test network Calaveras using the official file
#786
Labels
Config
Command line or config file related
Comments
|
jangko
added a commit
that referenced
this issue
Aug 5, 2021
- allow clique period and epoch to be configured via config file - this also activate poaEngine mode - remove clique period configuration from cli to reduce confusion - fix #786
jangko
added a commit
that referenced
this issue
Aug 5, 2021
- allow clique period and epoch to be configured via config file - this also activate poaEngine mode - remove clique period configuration from cli to reduce confusion - fix #786
jangko
added a commit
that referenced
this issue
Aug 5, 2021
- allow clique period and epoch to be configured via config file - this also activate poaEngine mode - remove clique period configuration from cli to reduce confusion - fix #786
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using this option
--customnetwork:calaveras.json
with or without--networkid:123
fails to result in a successful connection ot the Calaveras network, because genesis hash, network Id and probably other values are incorrect.The file
calaveras.json
is the JSON file in the Calaveras specification.In network logs some things are clear:
networkId
we are using is zero. It should be 123. This is visible in theeth.Status
message, but it's a missing value in the chain config, not the network code.eb9233d066c275efcdfed8037f4fc082770176aefdbcb7691c71da412a5670f2
but we have calculated2893a852a2fdec70cfb74307512489a2880c55703dcb623e3cf51300474af8d4
after setting up the genesis config.poaEngine: false
, but this is a PoA network, and is configured as such in the JSON file.Do we not support this file format?
The text was updated successfully, but these errors were encountered: