You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I 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.
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 active/available, and is this actually a bug or expected behavior?
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: