Bug: Parachain referenda tracks not displayed on Referenda page

[wischli]

• I'm submitting a ...

  • [x] Bug report
  • [x] Feature request
  • [ ] Support request
  • [ ] Other

• What is the current behavior and expected behavior?

The Referenda landing page /referenda only displays the 0/root track for parachains even though api.consts.referenda.tracks includes other entries. For instance, check Moonbeam: https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fwss.api.moonbeam.network#/referenda

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.

Referenda Page

Tracks

api.consts.referenda.tracks =
[[0, {name: root, maxDeciding: 5, decisionDeposit: 2000000000000000000000000, preparePeriod: 7200, decisionPeriod: 100800, confirmPeriod: 7200, minEnactmentPeriod: 7200, minApproval: {"reciprocal":{"factor":999999999,"xOffset":999999999,"yOffset":0}}, minSupport: {"linearDecreasing":{"length":1000000000,"floor":5000000,"ceil":250000000}}}], [1, {name: whitelisted_caller, maxDeciding: 100, decisionDeposit: 200000000000000000000000, preparePeriod: 50, decisionPeriod: 100800, confirmPeriod: 50, minEnactmentPeriod: 150, minApproval: {"reciprocal":{"factor":999999999,"xOffset":999999999,"yOffset":0}}, minSupport: {"reciprocal":{"factor":60061,"xOffset":2994150,"yOffset":-59882}}}], [2, {name: general_admin, maxDeciding: 10, decisionDeposit: 10000000000000000000000, preparePeriod: 300, decisionPeriod: 100800, confirmPeriod: 7200, minEnactmentPeriod: 7200, minApproval: {"reciprocal":{"factor":999999999,"xOffset":999999999,"yOffset":0}}, minSupport: {"reciprocal":{"factor":222222224,"xOffset":333333335,"yOffset":-166666668}}}], [3, {name: referendum_canceller, maxDeciding: 20, decisionDeposit: 200000000000000000000000, preparePeriod: 300, decisionPeriod: 100800, confirmPeriod: 900, minEnactmentPeriod: 50, minApproval: {"reciprocal":{"factor":999999999,"xOffset":999999999,"yOffset":0}}, minSupport: {"reciprocal":{"factor":869501,"xOffset":8620680,"yOffset":-862069}}}], [4, {name: referendum_killer, maxDeciding: 100, decisionDeposit: 400000000000000000000000, preparePeriod: 300, decisionPeriod: 100800, confirmPeriod: 900, minEnactmentPeriod: 50, minApproval: {"reciprocal":{"factor":999999999,"xOffset":999999999,"yOffset":0}}, minSupport: {"reciprocal":{"factor":869501,"xOffset":8620680,"yOffset":-862069}}}]]

• What is the motivation for changing the behavior?

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:

  • [ ] Node.js

  • [x] Browser: Brave Version 1.65.123 Chromium: 124.0.6367.91

  • [ ] Other (limited support for other environments)

  • Language:

  • [ ] JavaScript

  • [ ] TypeScript (include tsc --version)

  • [x] Other

[TarikGul]

Can confirm the above. I am able to see all the tracks in polkadot, but not moonbeam

[TarikGul]

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?