-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Bug: Parachain referenda tracks not displayed on Referenda page #10544
Comments
wischli
changed the title
Bug: Parachain referenda tracks not displayed
Bug: Parachain referenda tracks not displayed on Referenda page
May 6, 2024
Can confirm the above. I am able to see all the tracks in polkadot, but not moonbeam |
It's late so I am going to continue looking into this tomorrow, but a questions I have for myself would be: What makes a track |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm submitting a ...
What is the current behavior and expected behavior?
The Referenda landing page
/referenda
only displays the0/root
track for parachains even thoughapi.consts.referenda.tracks
includes other entries. For instance, check Moonbeam: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fwss.api.moonbeam.network#/referendaI have to admit that I did not check all parachains but I ran into this issue as part of adding OpenGov to Centrifuge Chain. I am running a chopsticks instance with a WASM override which includes OpenGov with several tracks.
Referenda Page
Tracks
It should mimic the relaychain because else tracks except for root can only be distinguished using external frontends.
Please tell us about your environment:
Version:
Environment:
Brave Version 1.65.123 Chromium: 124.0.6367.91
Language:
The text was updated successfully, but these errors were encountered: