A few concerns and clarification requests regarding this proposal:

1) Reliance on a centralized, closed-source indexer

At the moment, the PolkadotCloud Staking Dashboard appears to rely heavily on a centralized indexer. I previously opened a GitHub issue to ask (politely) about this dependency, but the issue was deleted rather than answered.

Could @Ross and Joel | Polkadot Cloud please clarify the following:

1. Open-source / transparency: Since the indexer has been funded via OpenGov, can the indexer code be made public?
2. Respecting user preferences: When a user selects to connect via the light-client, the SPA still appears to fetch most data from the centralized indexer. This feels misleading. Can you commit to honoring the selected connectivity mode (and not use the indexer when the user has indicated that they want to use the light-client)?
3. Issue deletion: Why was the GitHub issue deleted rather than addressed?
4. Resilience: Can you ensure the application remains functional (even if a bit slower) when the indexer is unavailable?

2) Analytics / tracking and user consent

Another concern is that the dashboard seems to track a large portion of user interactions without explicitly requesting consent.

Could you please:

• explain what is collected, why, and where it is sent/stored; and
• provide a way to disable analytics (opt-out), ideally with privacy-preserving defaults?

I strongly believe OpenGov-funded initiatives should meet a baseline privacy standard (explicit disclosure + user control).

3) Validator commission “flipping” UX mitigation

AFAIK the dashboard still hasn’t addressed the validator commission flipping UX issue discussed here:
https://forum.polkadot.network/t/are-validators-flipping-commissions-and-running-multiple-identities/16569/7?u=josep

This can be prevented all together with UI improvements (as shown in that thread). It’s concerning that it hasn’t been implemented yet, and the proposal doesn’t mention addressing it. Can you commit to adding safeguards / clearer warnings and surfacing recent commission history prominently?

Closing

To be clear: I’m not opposed to funding this initiative. I am asking that these issues be acknowledged and addressed with concrete commitments (and ideally scoped deliverables) before/alongside funding.

Thanks for considering these suggestions.

On behalf of the Web3 Foundation, we are voting AYE on Referendum #1831.

Following further internal reviews, our funding committee agrees that the Staking Dashboard has consistently provided good value for the Polkadot ecosystem. We particularly support the team’s direction toward increased decentralization via light client integration, which aligns with our shared technical priorities for the network.

We also appreciate that the team recognizes the dashboard as a public good and is prepared to move the repository and domain under the Polkadot Community Foundation as soon as the necessary mechanisms are in place. We would like to thank Joel and Ross for their consistent professionalism and responsiveness throughout our coordination over these past months.