Proposed by:
Requested amount:
0 DOT

#1370 · Polkadot Staking Dashboard 2025 (Q1-Q2) Funding Proposal

Overview

The full details of our proposal can be viewed here: Full Proposal on Google Docs.

1.1 Proposal Details

Proponents: Ross Bulat and Joel Kenny
Beneficiary Address: 13MNarAqpNkginnQb6gTNq2QnieZGs2SKu8JdK9LLxo6ksEP
Requested Amount: $82,000 USDT
Funding Period: January 2025 to June 2025 (6 months)
Planned Referendum Start Date: 3rd January 2025

We are pleased to present our proposal for continued development of the Polkadot Staking Dashboard for Q1-Q2 2025. Having successfully completed our previous milestones (verified via OG Tracker), we're confident the Dashboard is well-positioned for its next phase of development.

After careful consideration of community feedback and recent ecosystem developments, we have decided to focus this funding effort exclusively for the Staking Dashboard. This allows us to concentrate our resources on maintaining and enhancing this critical infrastructure serving a well-engaged user base.

Key points for this proposal:

  1. 6-month timeframe to provide clearer deliverables and reduced treasury risk
  2. Funding requested in USDT stablecoin per community preference
  3. Focused development roadmap targeting user experience and critical network upgrades
  4. Strengthened team structure with dedicated support channels and enhanced community engagement
  5. Continued commitment to open-source development and community engagement

What This Means For Users:

  1. Easier staking: Simpler interfaces for both direct staking and nomination pools
  2. Better rewards tracking: Enhanced features to monitor and collect staking rewards
  3. Mobile-friendly updates: Improved experience on phones and tablets
  4. Expanded language support: Adding Spanish translations to join existing Mandarin support, making staking more accessible globally
  5. Faster loading times: Technical improvements for better performance
  6. More secure staking: Enhanced error prevention and user guidance
  7. Enhanced support: New dedicated staking support email and Discord channel for rapid assistance
  8. Improved documentation: Restructured Resources section with a clear separation between basic and advanced features

1.2 Key Project Objectives

The Polkadot Staking Dashboard has become a cornerstone of network participation. Our objectives for Q1-Q2 2025 focus on:

  1. Improving staking accessibility and user experience. We are tackling this by streamlining the UI by minimising steps in flows, and rolling out a dedicated GraphQL plugin we’ve called the Staking API, that provides instant historical staking data. See Staking API Announcement on X.
  2. Implementing Plaza upgrade support. Staking (and governance) will soon be migrated to AssetHub; and Staking Dashboard needs to be refactored to support this migration to stay functional. This is a critical, high priority action item of this proposal.
  3. Supporting nomination pool bonding migration (migrating bonded pool funds to account locks), providing UI that allows users to see their nomination pool locks.
  4. Enhancing network security through broader staking participation.
  5. Maintain support for Smoldot and Polkadot API.

1.3 Project Vision

The Staking Dashboard aims to be the most accessible and reliable platform for Polkadot network participation.

Our vision encompasses:

  1. Simplified staking processes for users of all experience levels
  2. Dramatically speeding up dashboard sync times by utilising our blazing fast Staking API plugin
  3. Robust support for network upgrades and features
  4. Enhanced user education and support
  5. Global accessibility through multi-language support

Deliverables

2.1 Staking Dashboard Enhancements

High-Level Staking Dashboard Objectives:

  1. Enhance User Experience: Streamline key staking flows utilising our latest Staking API, community feedback and improved UI design. Flows of interest include nominator setup, managing nominations, joining a pool, and destroying a pool
  2. Maintain Core Infrastructure: Support network upgrades, security patches, and API transitions
  3. Expand Features: Add portfolio analytics, validator tools, and reward optimization features
  4. Improve Accessibility: Integrate educational resources and risk assessment tools while maintaining advanced options.

While we maintain detailed internal timelines, we avoid rigid public deadlines given Polkadot's evolving ecosystem and upcoming network upgrades. This approach lets us prioritize the most impactful features while remaining responsive to:

  1. Network upgrades and technical requirements
  2. Community feedback and user needs
  3. New staking mechanisms and features
  4. Security considerations and best practices.
  5. Deliverables Breakdown:

 

Support “Plaza” upgrades in relation to staking as they are deployed

Plaza is a major refactor that brings chain logic, including staking and nomination pools, from the Relay Chain to the AssetHub system chain. Staking dashboard will, therefore, need to be updated to support this migration by supporting AssetHub as an additional chain.

 

Support nomination pool bonding migration

Ensure the pool bonding mechanism stays intact amid the nomination pool bonding migration, that allows users to maintain voting rights while staked to a pool, Kusama and Polkadot migration is yet to be activated.

Prior to this migration, nomination pool members (and owners) must transfer their funds to the nomination pool’s stash address in order to participate. By doing this, it is no longer possible for members to vote in OpenGov. This migration fixes this shortcoming.

 

Streamline wallet connection interface

Implement unified connect interface to simplify wallet connections and reduce UI complexity. This action item will simplify Staking Dashboard’s wallet connection flow.

 

Layout plans to sunset the need for staking support in JS Apps

Provide comprehensive migration guides and tools to help users transition from JS Apps staking to the Dashboard, ensuring continuity of user experience and feature parity.

 

Improve application architecture

Provide an intuitive API to interact with all supported chains connected on the dashboard. E.g. have the same bootstrapping of network consts & configs for AssetHub and People Chain as the Relay Chain. Critical for enabling transaction submission on AssetHub.

 

Continued support of general dependency updates / refactors as dependencies roll out / breaking changes

Critical to keep Staking Dashboard up to date using industry-standard dependencies as they are updated.

 

Introduce "Easy Mode" staking setup with additional educational content

Create a simplified onboarding flow for new users that focuses on essential information and basic staking concepts. Advanced features and technical data will be optional/hidden to prevent information overload.

 

Speed up and streamline one click pool joining

Move one-click pool joining syncing from node to Staking API that will provide all the necessary data to join a pool in one query. Currently, it can take a long time to sync multiple era data to determine pool performance with the light client / RPC node.

 

Rewards calculator

Rewards calculator: Interactive tool to estimate potential returns

 

Share / invite links

Enable validators/pools to create direct nomination links

 

Improved nomination management

Managing nominations can be improved in a number of ways, including allowing searching of validators directly in the UI, introducing filters such as only selecting validators within a commission threshold, and more intuitive UI, such as showing selection boxes by default, and allowing inline removal of validators.

 

Resources section overhaul

Restructure documentation into tiered learning paths with: - Essential guides for new users - Advanced documentation for power users - Clear navigation between basic/advanced features - Improved searchability and organization.

 

Improved multi-language support

With approximately 30% of our users coming from Spanish-speaking regions, we will expand our language support to include Spanish translations, building on our existing Mandarin localization. This expansion of interface, documentation, and educational resources reflects our commitment to global accessibility.

 

GraphQL Staking API plugin growth

Continue the rollout of Staking API GraphQL plugin, that is playing a role of dramatically speeding up the staking dashboard.

Readers can test the Staking API directly on Apollo’s GraphQL Sandbox: https://studio.apollographql.com/sandbox/explorer?endpoint=https://api.staking.polkadot.cloud

 

Continued Staking Dashboard hosting at https://staking.polkadot.cloud

Serving as the primary staking interface for the Polkadot ecosystem.

 

2.2 Significance to Polkadot's Security

The Staking Dashboard plays a vital role in Polkadot's ecosystem by:

  1. Providing an intuitive gateway for users to participate in network security
  2. Supporting both direct staking and nomination pools
  3. Ensuring smooth transitions during network upgrades
  4. Offering comprehensive staking education and guidance
  5. Maintaining open-source code for ecosystem transparency
  6. Broadening global accessibility through strategic language expansion, with Spanish joining Mandarin to serve our diverse user base

 

2.3 Development Framework

Our development approach prioritizes:

  1. Regular community updates and feedback cycles
  2. Flexibility to adapt to network upgrades and requirements
  3. Focus on security and stability
  4. Clear progress tracking via GitHub
  5. Responsive bug fixes and support

We structure development while maintaining flexibility for critical updates and community needs. This ensures steady progress while allowing us to adapt to ecosystem changes and user feedback.

All code remains open source, enabling community review and contribution.

Team

For detailed team information, visit the Full Proposal: Team section.

Community Engagement and Feedback

For detailed plans on community engagement and contributions, visit the Full Proposal: Community Engagement and Feedback section.

Budget

For detailed budgetting, visit the Full Proposal: Budget section.

Conclusion

This proposal seeks $82,000 USDT to enhance the Polkadot Staking Dashboard over six months (January-June 2025). Having recently completed our outstanding commitments and with a well-engaged user base, our focused roadmap aims to:

  1. Support critical network upgrades as they roll out, like reduced unbonding times and Plaza integration
  2. Improve staking accessibility with streamlined UI and multi-language features
  3. Implement new pool creation and destroying mechanisms for better user control
  4. Further roll out Staking API to turbo charge dashboard speed and reliability.

The Staking Dashboard has established itself as essential infrastructure for Polkadot's network security. Our streamlined six-month timeline and concentrated scope demonstrate our commitment to delivering tangible value while minimizing treasury risk.

We invite the community to support this proposal and help us continue making staking more accessible to all Polkadot users.

Questions? Comments? Give us your feedback below!

Kind Regards,

Ross Bulat & Joel Kenny

Read more
StatusExecuted
99%Aye
Aye (232)
32.82M DOT
Nay (18)
91.020K DOT
Decision28 / 28d
Confirmation4 / 4d
0.0%0.50%
0.12%Support Threshold
0Support Threshold
Support(0.40%)
≈ 6.11M DOT
Issuance
≈ 1.53B DOT
Vote
ChaosDAOJan 21

ChaosDAO would like to provide the following feedback from our community. We offer this feedback voluntarily in the spirit of OpenGov, in order to help teams improve their proposals so we can all build the network together.

  1. Some members expressed concerns about the quality/UX of the staking dashboard.

  2. Some members pointed out that although the staking dashboard needs a lot of improvements, it is wildly used by the ecosystem.

  3. Some members expressed concerns about the nature of the proponent's response to feedback.

ChaosDAO votes as a collective based on the results of our anonymous internal voting procedures. Our members are not required to provide any feedback about why they have voted in a particular direction. Similarly, to respect our members' right to anonymity, we will not be sharing the names of individuals who have chosen to voluntarily provide feedback. You can find out more about how we vote and how to get in contact with us here: https://x.com/ChaosDAO/status/1762986093316587995

The_Kus_DAOJan 10

Kus DAO have voted AYE (first voting).

✅ Enhanced staking tools, mobile-friendly updates, and better rewards tracking for users.

❌ None.

 

💪 Get involved: 🔗 Discord Invite or Telegram Invite

💬 Join the discussion: 🔗 Discussion Thread

~@_Pieky_

LuckyFridayGovProxyJan 10

Lucky Friday have voted AYE. Please consider this a temporary notification after our vote has gone on chain. If you would like additional feedback on our rationale for this vote, please join our OpenGov Public Forum on Telegram here: https://t.me/+559tyPSfmGg0NzUx

Lucky Friday provides feedback once per week (Fridays) if specifically requested in our OpenGov Public Forum, and we respectfully ask that all proponents of referenda interact with us here for the sake of transparency. Please tag our Director of Protocol Relations “Phunky” with your referendum number so that he can gather the relevant commentary from our internal deliberations.

Ross_and_JoelJan 7
ltfschoen

Questions:

  1. How many chains, and their validators, and nominators in the Polkadot ecosystem are currently excluded from being able to use the current Polkadot Staking Dashboard?

  2. What new users are going to be seamlessly onboarded through "enhancements" that you will make using the funds in this proposal? Is it going to be designed so that minimal configuration is required for them to be onboarded?

  3. With regards to "enhancing" the Polkadot Staking Dashboard, will the funding in this proposal go towards onboarding and supporting Parachains and Substrate-based Stand-alone chains (aka solo chains) that currently want to use it but can't? At the moment, the Polkadot Staking Dashboard currently only appears to support Relay chains, and System Parachains (People Chains).

  4. A Non-System parachain may have a coretime lease that expires, and it may be necessary for them to temporarily switch to being a Stand-alone chain (aka solo chain), but if that happened would their community still be able to use the Polkadot Staking Dashboard?

  5. A Stand-alone Chain may not want the extra complexity of using the People Chain for identities, but if they chose not to would they still be able to seamlessly configure and use the Polkadot Staking Dashboard?

  6. If the Polkadot Staking Dashboard gets "enhanced" to support Non-System Parachains and Stand-alone Chains, will it only work if their chain supports light clients by its implementation support for the sc-sync-state-rpc crate (a light sync state extension) from the Polkadot SDK?

  7. If a Non-System Parachain or Stand-alone Chain wants to fork the https://github.com/w3ux/w3ux-library repository using a branch "my-branch" and the https://github.com/polkadot-cloud/polkadot-staking-dashboard repository and change each import in the Polkadot Staking Dashboard repository to use the the relevant @w3ux workspace package in that branch using the latest Yarn 4.6.0 syntax, how would they do that so the dependencies get installed and transpiled correctly in their fork? For example, if they needed to import the "@w3ux/hooks" workspace package, would they importing it like this in the package.json file "@w3ux/hooks": "[email protected]:my-fork-repo/w3ux-library.git#head=my-branch&workspace=@w3ux/hooks", or would they need to rename anything to "@w3ux/hooks-source" to match the name of that workspace package?

  8. In Section 3.1 of the Full Proposal https://docs.google.com/document/d/1tDo4D7tDabSDR9D8dAPkZcKB88NzyBQDu-Vx4w9gA_M/edit?tab=t.0, it says each of the two team members will be committing 25 hours per week, and in Section 2.1 it says that you'll be able to prioritize the most impactful features while remaining responsive to community feedback and user needs, and in Section 2.3 it says that your development approach prioritizes support. How many hours per week are allocated to mentoring the Polkadot Cloud Contribution Program?

  9. In Section 4.3 Polkadot Cloud Contribution Program, it says that it only supports the Supported Repository: Polkadot Staking Dashboard. If the scope of the Polkadot Staking Dashboard remains contrained to only supporting Relay Chains and System Parachains, and other developers are required to fork the Polkadot Staking Dashboard to add those features for their individual Non-System parachain or Stand-alone chain (aka solo chain) that they share for others, but any pull requests that they make into the official Polkadot Staking Dashboard repository aren't reviewed or approved, will they be in any way eligible for the Polkadot Cloud Contribution Program?

  10. In Section 4.4 it says "Throughout the project, we will maintain: Ongoing collaboration with Polkadot core developers.". How do you define a "Polkadot core developer"? How many hours per week go towards collaboration? Are those in the Polkadot Fellowship above a certain grade the only ones that are eligible for ongoing collaboration, whilst others are subject to adhoc collaboration?

@ltfschoen Thank you for taking the time to review our proposal in such detail and for sharing these thoughtful questions. We appreciate your interest in expanding the reach and capabilities of the Polkadot Staking Dashboard.

Technical Implementation and Chain Support:

Currently, the Polkadot Staking Dashboard serves as the dedicated staking application for Polkadot, Kusama and Westend relay chains, and their System chains. Maintaining this focused scope allows us to deliver the highest quality experience possible for these networks. While we’re open to the idea of adding more chains, there are significant technical challenges involved, including:

  • Determining which pallets are on which chain.
  • Configuring light client chain specs for Smoldot.
  • Setting up reliable RPC endpoints.
  • Ensuring Staking API support for historical data across additional networks.
  • Fetching and adapting identity data from alternative sources, which would require chain-specific configuration.

It’s worth noting that Smoldot can support any chain built with the Polkadot SDK, provided the appropriate chain specs, boot nodes, and other configurations are available. We encourage teams to explore forking the dashboard to adapt it to their specific needs, and we’re happy to collaborate by providing documentation, guidance, and support through Discord channels.

Contributions and Community Engagement:

The Polkadot Cloud Contribution Program focuses on enhancing the dashboard’s core functionality while onboarding developers to the ecosystem. Contributions through this program must align with internal goals and are closely mentored by our team. While PRs from external developers are welcome, they must be agreed upon and guided by our team to ensure consistency and alignment with project priorities.

We treat requests from the Contribution Program as high priority, as onboarding developers benefits not only the dashboard but also Polkadot Dapps as a whole. Allotted hours depend on demand, and we actively collaborate with Polkadot core developers—those maintaining relevant Polkadot SDK code—whether or not they are part of the Fellowship or other collectives.

Usability and API Advancements:

For new users, we’re streamlining the nominator setup process and introducing features like "Easy Mode" to simplify staking. Our primary goal is to ensure an exceptional experience for existing users while gradually improving usability and accessibility.

Licensing and Technical Details:

Regarding w3ux, it is licensed under GPL-3.0, meaning developers are free to fork it and publish new packages under their scope. The source packages only include the source code, with the builder package responsible for generating distributables for NPM. We’re happy to dive deeper into w3ux's functionality or other technical details on our Discord support channel.

We greatly value your feedback and are eager to collaborate further. Let’s continue our technical discussions in the dedicated ticket you created in the Polkadot Staking Dashboard Discord to provide more comprehensive insights. Thank you for your thoughtful engagement, and we look forward to working together to push the dashboard’s capabilities even further.

ltfschoenJan 6

Questions:

  1. How many chains, and their validators, and nominators in the Polkadot ecosystem are currently excluded from being able to use the current Polkadot Staking Dashboard?

  2. What new users are going to be seamlessly onboarded through "enhancements" that you will make using the funds in this proposal? Is it going to be designed so that minimal configuration is required for them to be onboarded?

  3. With regards to "enhancing" the Polkadot Staking Dashboard, will the funding in this proposal go towards onboarding and supporting Parachains and Substrate-based Stand-alone chains (aka solo chains) that currently want to use it but can't? At the moment, the Polkadot Staking Dashboard currently only appears to support Relay chains, and System Parachains (People Chains).

  4. A Non-System parachain may have a coretime lease that expires, and it may be necessary for them to temporarily switch to being a Stand-alone chain (aka solo chain), but if that happened would their community still be able to use the Polkadot Staking Dashboard?

  5. A Stand-alone Chain may not want the extra complexity of using the People Chain for identities, but if they chose not to would they still be able to seamlessly configure and use the Polkadot Staking Dashboard?

  6. If the Polkadot Staking Dashboard gets "enhanced" to support Non-System Parachains and Stand-alone Chains, will it only work if their chain supports light clients by its implementation support for the sc-sync-state-rpc crate (a light sync state extension) from the Polkadot SDK?

  7. If a Non-System Parachain or Stand-alone Chain wants to fork the https://github.com/w3ux/w3ux-library repository using a branch "my-branch" and the https://github.com/polkadot-cloud/polkadot-staking-dashboard repository and change each import in the Polkadot Staking Dashboard repository to use the the relevant @w3ux workspace package in that branch using the latest Yarn 4.6.0 syntax, how would they do that so the dependencies get installed and transpiled correctly in their fork? For example, if they needed to import the "@w3ux/hooks" workspace package, would they importing it like this in the package.json file "@w3ux/hooks": "[email protected]:my-fork-repo/w3ux-library.git#head=my-branch&workspace=@w3ux/hooks", or would they need to rename anything to "@w3ux/hooks-source" to match the name of that workspace package?

  8. In Section 3.1 of the Full Proposal https://docs.google.com/document/d/1tDo4D7tDabSDR9D8dAPkZcKB88NzyBQDu-Vx4w9gA_M/edit?tab=t.0, it says each of the two team members will be committing 25 hours per week, and in Section 2.1 it says that you'll be able to prioritize the most impactful features while remaining responsive to community feedback and user needs, and in Section 2.3 it says that your development approach prioritizes support. How many hours per week are allocated to mentoring the Polkadot Cloud Contribution Program?

  9. In Section 4.3 Polkadot Cloud Contribution Program, it says that it only supports the Supported Repository: Polkadot Staking Dashboard. If the scope of the Polkadot Staking Dashboard remains contrained to only supporting Relay Chains and System Parachains, and other developers are required to fork the Polkadot Staking Dashboard to add those features for their individual Non-System parachain or Stand-alone chain (aka solo chain) that they share for others, but any pull requests that they make into the official Polkadot Staking Dashboard repository aren't reviewed or approved, will they be in any way eligible for the Polkadot Cloud Contribution Program?

  10. In Section 4.4 it says "Throughout the project, we will maintain: Ongoing collaboration with Polkadot core developers.". How do you define a "Polkadot core developer"? How many hours per week go towards collaboration? Are those in the Polkadot Fellowship above a certain grade the only ones that are eligible for ongoing collaboration, whilst others are subject to adhoc collaboration?

JoelJKRBJan 6

@14rp4CvtyN3WSftrndyNxjJFi4cGXsgrE9gFr528QSYFvPTu — Thank you for your comprehensive feedback and support; it is much appreciated.

Jan 6

Dear @Ross and Joel | Polkadot Cloud,

Thank you for your proposal. Our vote on this proposal is AYE.

The Medium Spender track requires a 50% quorum and simple majority according to our voting policy. This proposal has received seven aye and zero nay votes from ten members. Below is a summary of our members' comments:

> The referendum received unanimous support, with members praising the proposer for responding to community feedback and presenting a well-structured, detailed proposal. The clear focus on staking, low budget of 82K, and outlined objectives, timeline, and team impressed voters. Members highlighted the proposal’s improvements over previous versions and expressed confidence in the team’s ability to deliver meaningful results.

The full discussion, along with individual members' votes and comments, can be found in our internal voting.

Kind regards,
Permanence DAO

JoelJKRBJan 6
Nik

Amazing Proposal and Very Timely
Staking will be the primary use case for the current ecosystem. The better our staking mechanism, the better the token’s price & community vibes. 
100% support

@Nik — thank you for your kind words and support.

Ross_and_JoelJan 5
Nik

Amazing Proposal and Very Timely
Staking will be the primary use case for the current ecosystem. The better our staking mechanism, the better the token’s price & community vibes. 
100% support

@Nik 🫡 

NikJan 4

Amazing Proposal and Very Timely
Staking will be the primary use case for the current ecosystem. The better our staking mechanism, the better the token’s price & community vibes. 
100% support

rossbulatJan 3
TINY

The Staking Dashboard is a crucial product for improving interactivity and is highly significant for the Polkadot ecosystem.
Polkadot Cloud has also consistently provided excellent products and services.
However, we’ve been trying to reach out to you on Element but haven’t received any response so far.😮‍💨

@TINY Thanks so much for the positive comments Tiny! I've set up a group chat in Element, let's discuss more there.

TINYJan 3

The Staking Dashboard is a crucial product for improving interactivity and is highly significant for the Polkadot ecosystem.
Polkadot Cloud has also consistently provided excellent products and services.
However, we’ve been trying to reach out to you on Element but haven’t received any response so far.😮‍💨

Powered by Subsocial