-
Notifications
You must be signed in to change notification settings - Fork 95
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
Parachain nodes are not peering with default config #171
Comments
Is
And according to these it is not:
If anyone can shed some light on this that would be great. |
I am really experiencing this same issue. |
polkadot-launch itself will add the flag A pair of things to check here then:
If the configuration doesn't deviates much from a default config these should be one of the few checks to make for the parachain working as expected. For more custom chain specs and set ups the possible points of failure may vary |
For parachain node peering to work for me, I had to replace the "id": "200", with the "chain": "statemine-dev", then my parachain nodes peer, otherwise they do not. Here is my config for reference: |
Alright... Thanks so much, will try this out and give you feedback. |
Closing this as it has resolved the stated issue. @dharjeezy if you are still having issues with running yours I would recommend opening a small replicable concise question on substrate.stackexchange.com as polkadot-launch does seem to be peering parachain nodes fine. |
Using the default config with an additional parachain node, the relay-chain node and the parachain nodes are up and running but the parachain nodes are not peering. If I add the
--force-authoring
flag to the parachain nodes, the parachain starts creating blocks.The text was updated successfully, but these errors were encountered: