-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Two different peer id, for single node. #52
Comments
This is probably because your chain spec file contains one boot node address, but your bootnode itself advertises a different one. For this tutorial, there should not be any bootnodes in your chainspec file. Please open your "bootNodes": [], If that list contains an actual bootnode, please remove it, and try again. If you followed the tutorial exactly you shouldn't end up in this situation because https://www.substrate.io/tutorials/start-a-private-network/v2.0.0-rc2/customspec#create-a-chain-specification says to generate your custom spec using this command. # Export the local chainspec to json
$ ./target/release/node-template build-spec --disable-default-bootnode --chain local > customSpec.json When you include |
Yup, thanks. |
Hi, I do have similar issue with the following error: Can assist on this issue? Thank you |
Can you describe what are you doing when you encounter this error? Were you working with chain specs? If so, how did you generate them? |
* Super Node Runtime compiles * Basic example of default config. * One crate per config. In hopes of combining configs with runtimes later. * fix some typos * add basic-token config, update some deps * check-membership * double-map * linked-map * module constants with Get * schedule on finalize * simple-map * add simple events and storage; order existing from easy to hard * storage-cache example * push to merge * Add wrapper node to kitchen
these are not needed for collators.
I was going through the
starting your own private network with https://www.substrate.io/tutorials/start-a-private-network/v2.0.0-rc2
. I generated keys with subkey. Created chainspec, started node 1 and node2 . But node 2 failed withId
QmYb6raWsGsw5rpncKW2iJUBTxP3SdFy8KzjofaEtBAiJy
was printed in logs of node1. But using it as bootnode peer id for node2 failed. UsingQmYkKnqtB46sufgYSPUBCFUdYn8ipvZ1H8jSDzvpMjx6wp
worked and I was successfully able to complete it.Why is node1 printing a peer id and using another peer one?
The text was updated successfully, but these errors were encountered: