-
Notifications
You must be signed in to change notification settings - Fork 700
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
Missing the Polkadot People Chain chain-spec #5112
Comments
It exists here: https://github.com/paseo-network/runtimes/tree/main/chain-specs |
I'm afraid that you got mixed up, those are the chain-specs of Paseo. This issue is about the chain-spec of the Polkadot People Chain. |
🤦🏽 Ufff... too many parallel things going on. Thank you for straighting this up @josepot |
Hi @josepot. The Polkadot People chainspec was included as an asset in the Fellows runtime 1.2.6 release here: https://github.com/polkadot-fellows/runtimes/releases/tag/v1.2.6 The hardcoded system parachain chain specs will soon be removed from |
Thanks! Although, those bootnodes are all from Parity... where can we get a more complete list of bootnodes?
This would make a lot of sense if the RFC-8 had been implemented, as we could obtain the list of parachain bootnodes from the relay-chain. However, until that's not a reality, then we will need some sort of "authoritative" place for retrieving the bootnodes of the parachains. |
Good point, I've added it to the sdk repo in #5124 so we have something in place until a better solution is found. RE the bootnodes, there are five community invulnerables here but none marked as boot nodes at launch. I think usually the community add theirs afterwards in PRs like this one. This is another point for keeping the chain specs somewhere which can be edited and changes tracked. For the Polkadot Coretime Chain I'll also gather some of these community boot nodes before launch. |
Exactly, yes. Thanks! This is exactly what I meant.
🙌 |
Published as part of the fellowship [v1.2.6](https://github.com/polkadot-fellows/runtimes/releases/tag/v1.2.6) release and originally intentionally left out of the repo as the hardcoded system chains will soon be removed from the `polkadot-parachain`. After a conversation in #5112 it was pointed out by @josepot that there should be a single authoritative source for these chainspecs. Since this is already the place for these it will serve until something more fitting can be worked out.
Published as part of the fellowship [v1.2.6](https://github.com/polkadot-fellows/runtimes/releases/tag/v1.2.6) release and originally intentionally left out of the repo as the hardcoded system chains will soon be removed from the `polkadot-parachain`. After a conversation in paritytech#5112 it was pointed out by @josepot that there should be a single authoritative source for these chainspecs. Since this is already the place for these it will serve until something more fitting can be worked out.
As of today the Polkadot People Chain chain-spec is nowhere to be found on this repo. Would it be possible to add it into the same directory where all the other system-chain-specs are? 🙏
Also, FWIW if RFC-8 was implemented, then we wouldn't need this chain-spec 😉
The text was updated successfully, but these errors were encountered: