The full details of our proposal can be viewed here: Full Proposal on Google Docs.
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:
What This Means For Users:
The Polkadot Staking Dashboard has become a cornerstone of network participation. Our objectives for Q1-Q2 2025 focus on:
The Staking Dashboard aims to be the most accessible and reliable platform for Polkadot network participation.
Our vision encompasses:
High-Level Staking Dashboard Objectives:
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:
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.
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.
Implement unified connect interface to simplify wallet connections and reduce UI complexity. This action item will simplify Staking Dashboard’s wallet connection flow.
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.
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.
Critical to keep Staking Dashboard up to date using industry-standard dependencies as they are updated.
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.
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: Interactive tool to estimate potential returns
Enable validators/pools to create direct nomination links
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.
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.
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.
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
Serving as the primary staking interface for the Polkadot ecosystem.
The Staking Dashboard plays a vital role in Polkadot's ecosystem by:
Our development approach prioritizes:
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.
For detailed team information, visit the Full Proposal: Team section.
For detailed plans on community engagement and contributions, visit the Full Proposal: Community Engagement and Feedback section.
For detailed budgetting, visit the Full Proposal: Budget section.
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:
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
Threshold
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 full discussion, along with individual members' votes and comments, can be found in our internal voting.
Kind regards,
Permanence DAO