<h1><img src="https://i.ibb.co/55dZBJd/og-image.png" alt="" width="640" height="336" /></h1>
<h1 id="overview"><strong>Overview</strong></h1>
<p>The full details of our proposal can be viewed here: <a href="https://docs.google.com/document/d/1tDo4D7tDabSDR9D8dAPkZcKB88NzyBQDu-Vx4w9gA_M/edit?usp=sharing" target="_blank" rel="noopener">Full Proposal on Google Docs</a>.</p>
<h2 id="11proposaldetails"><strong>1.1 Proposal Details</strong></h2>
<p><strong>Proponents</strong>: Ross Bulat and Joel Kenny<br /><strong>Beneficiary Address</strong>: 13MNarAqpNkginnQb6gTNq2QnieZGs2SKu8JdK9LLxo6ksEP<br /><strong>Requested Amount</strong>: $82,000 USDT<br /><strong>Funding Period</strong>: January 2025 to June 2025 (6 months)<br /><strong>Planned Referendum Start Date</strong>: 3rd January 2025</p>
<hr />
<p>We are pleased to&nbsp;present our proposal for continued development of the <a href="http://staking.polkadot.cloud" target="_blank" rel="noopener">Polkadot Staking Dashboard</a> for Q1-Q2 2025. Having successfully completed our previous milestones (<a href="https://app.ogtracker.io/mediumSpender/355" target="_blank" rel="noopener">verified via OG Tracker</a>), we're confident the Dashboard is well-positioned for its next phase of development.</p>
<p>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.</p>
<p><strong>Key points for this proposal:</strong></p>
<ol>
<li>6-month timeframe to provide clearer deliverables and reduced treasury risk</li>
<li>Funding requested in USDT stablecoin per community preference</li>
<li>Focused development roadmap targeting user experience and critical network upgrades</li>
<li>Strengthened team structure with dedicated support channels and enhanced community engagement</li>
<li>Continued commitment to open-source development and community engagement</li>
</ol>
<p><strong>What This Means For Users:</strong></p>
<ol>
<li><strong>Easier staking</strong>: Simpler interfaces for both direct staking and nomination pools</li>
<li><strong>Better rewards tracking</strong>: Enhanced features to monitor and collect staking rewards</li>
<li><strong>Mobile-friendly updates</strong>: Improved experience on phones and tablets</li>
<li><strong>Expanded language support</strong>: Adding Spanish translations to join existing Mandarin support, making staking more accessible globally</li>
<li><strong>Faster loading times</strong>: Technical improvements for better performance</li>
<li><strong>More secure staking</strong>: Enhanced error prevention and user guidance</li>
<li><strong>Enhanced support</strong>: New dedicated staking support email and Discord channel for rapid assistance</li>
<li><strong>Improved documentation</strong>: Restructured Resources section with a clear separation between basic and advanced features</li>
</ol>
<p>&nbsp;</p>
<h2 id="12keyprojectobjectives"><strong>1.2 Key Project Objectives</strong></h2>
<p>The Polkadot Staking Dashboard has become a cornerstone of network participation. Our objectives for Q1-Q2 2025 focus on:</p>
<ol>
<li>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&rsquo;ve called the Staking API, that provides instant historical staking data. See <a href="https://x.com/rossbulat/status/1872871020761387464" target="_blank" rel="noopener">Staking API Announcement on X</a>.</li>
<li>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.</li>
<li>Supporting nomination pool bonding migration (migrating bonded pool funds to account locks), providing UI that allows users to see their nomination pool locks.</li>
<li>Enhancing network security through broader staking participation.</li>
<li>Maintain support for Smoldot and Polkadot API.</li>
</ol>
<p>&nbsp;</p>
<h2 id="13projectvision"><strong>1.3 Project Vision</strong></h2>
<p>The Staking Dashboard aims to be the most accessible and reliable platform for Polkadot network participation.</p>
<p>Our vision encompasses:</p>
<ol>
<li>Simplified staking processes for users of all experience levels</li>
<li>Dramatically speeding up dashboard sync times by utilising our blazing fast Staking API plugin</li>
<li>Robust support for network upgrades and features</li>
<li>Enhanced user education and support</li>
<li>Global accessibility through multi-language support</li>
</ol>
<p>&nbsp;</p>
<h1 id="deliverables">Deliverables</h1>
<h2 id="deliverables"><img src="https://i.ibb.co/vxvLVrw/Staking-Hero.png" alt="" width="600" height="365" /></h2>
<h2 id="21stakingdashboardenhancements"><strong>2.1 Staking Dashboard Enhancements</strong></h2>
<p>High-Level Staking Dashboard Objectives:</p>
<ol>
<li><strong>Enhance User Experience</strong>: 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</li>
<li><strong>Maintain Core Infrastructure</strong>: Support network upgrades, security patches, and API transitions</li>
<li><strong>Expand Features</strong>: Add portfolio analytics, validator tools, and reward optimization features</li>
<li><strong>Improve Accessibility</strong>: Integrate educational resources and risk assessment tools while maintaining advanced options.</li>
</ol>
<p>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:</p>
<ol>
<li>Network upgrades and technical requirements</li>
<li>Community feedback and user needs</li>
<li>New staking mechanisms and features</li>
<li>Security considerations and best practices.</li>
<li>Deliverables Breakdown:</li>
</ol>
<h4>&nbsp;</h4>
<h4 id="supportplazaupgradesinrelationtostakingastheyaredeployed">Support &ldquo;Plaza&rdquo; upgrades in relation to staking as they are deployed</h4>
<p>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.</p>
<h4>&nbsp;</h4>
<h4 id="supportnominationpoolbondingmigration">Support nomination pool bonding migration</h4>
<p>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.</p>
<p>Prior to this migration, nomination pool members (and owners) must transfer their funds to the nomination pool&rsquo;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.</p>
<h4>&nbsp;</h4>
<h4 id="streamlinewalletconnectioninterface">Streamline wallet connection interface</h4>
<p>Implement unified connect interface to simplify wallet connections and reduce UI complexity. This action item will simplify Staking Dashboard&rsquo;s wallet connection flow.</p>
<h4>&nbsp;</h4>
<h4 id="layoutplanstosunsettheneedforstakingsupportinjsapps">Layout plans to sunset the need for staking support in JS Apps</h4>
<p>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.</p>
<h4>&nbsp;</h4>
<h4 id="improveapplicationarchitecture">Improve application architecture</h4>
<p>Provide an intuitive API to interact with all supported chains connected on the dashboard. E.g. have the same bootstrapping of network consts &amp; configs for AssetHub and People Chain as the Relay Chain. Critical for enabling transaction submission on AssetHub.</p>
<h4>&nbsp;</h4>
<h4 id="continuedsupportofgeneraldependencyupdatesrefactorsasdependenciesrolloutbreakingchanges">Continued support of general dependency updates / refactors as dependencies roll out / breaking changes</h4>
<p>Critical to keep Staking Dashboard up to date using industry-standard dependencies as they are updated.</p>
<h4>&nbsp;</h4>
<h4 id="introduceeasymodestakingsetupwithadditionaleducationalcontent">Introduce "Easy Mode" staking setup with additional educational content</h4>
<p>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.</p>
<h4>&nbsp;</h4>
<h4 id="speedupandstreamlineoneclickpooljoining">Speed up and streamline one click pool joining</h4>
<p>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.</p>
<h4>&nbsp;</h4>
<h4 id="rewardscalculator">Rewards calculator</h4>
<p>Rewards calculator: Interactive tool to estimate potential returns</p>
<h4>&nbsp;</h4>
<h4 id="shareinvitelinks">Share / invite links</h4>
<p>Enable validators/pools to create direct nomination links</p>
<h4>&nbsp;</h4>
<h4 id="improvednominationmanagement">Improved nomination management</h4>
<p>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.</p>
<h4>&nbsp;</h4>
<h4 id="resourcessectionoverhaul">Resources section overhaul</h4>
<p>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.</p>
<h4>&nbsp;</h4>
<h4 id="improvedlultilanguagesupport">Improved multi-language support</h4>
<p>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.</p>
<h4>&nbsp;</h4>
<h4 id="graphqlstakingapiplugingrowth">GraphQL Staking API plugin growth</h4>
<p>Continue the rollout of Staking API GraphQL plugin, that is playing a role of dramatically speeding up the staking dashboard.</p>
<p>Readers can test the Staking API directly on Apollo&rsquo;s GraphQL Sandbox: <a href="https://studio.apollographql.com/sandbox/explorer?endpoint=https://api.staking.polkadot.cloud">https://studio.apollographql.com/sandbox/explorer?endpoint=https://api.staking.polkadot.cloud</a></p>
<h4>&nbsp;</h4>
<h4 id="continuedstakingdashboardhostingathttpsstakingpolkadotcloud">Continued Staking Dashboard hosting at <a href="https://staking.polkadot.cloud">https://staking.polkadot.cloud</a></h4>
<p>Serving as the primary staking interface for the Polkadot ecosystem.</p>
<h3>&nbsp;</h3>
<h2 id="22significancetopolkadotssecurity"><strong>2.2 Significance to Polkadot's Security</strong></h2>
<p>The Staking Dashboard plays a vital role in Polkadot's ecosystem by:</p>
<ol>
<li>Providing an intuitive gateway for users to participate in network security</li>
<li>Supporting both direct staking and nomination pools</li>
<li>Ensuring smooth transitions during network upgrades</li>
<li>Offering comprehensive staking education and guidance</li>
<li>Maintaining open-source code for ecosystem transparency</li>
<li>Broadening global accessibility through strategic language expansion, with Spanish joining Mandarin to serve our diverse user base</li>
</ol>
<h3>&nbsp;</h3>
<h2 id="23developmentframework"><strong>2.3 Development Framework</strong></h2>
<p>Our development approach prioritizes:</p>
<ol>
<li>Regular community updates and feedback cycles</li>
<li>Flexibility to adapt to network upgrades and requirements</li>
<li>Focus on security and stability</li>
<li>Clear progress tracking via GitHub</li>
<li>Responsive bug fixes and support</li>
</ol>
<p>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.</p>
<p>All code remains open source, enabling community review and contribution.</p>
<p>&nbsp;</p>
<h1 id="team"><strong>Team</strong></h1>
<p>For detailed team information, visit the <a href="https://docs.google.com/document/d/1tDo4D7tDabSDR9D8dAPkZcKB88NzyBQDu-Vx4w9gA_M/edit?tab=t.0#heading=h.n4631ru1hy7m" target="_blank" rel="noopener">Full Proposal: Team</a> section.</p>
<p>&nbsp;</p>
<h1 id="communityengagementandfeedback"><strong>Community Engagement and Feedback</strong></h1>
<p>For detailed plans on community engagement and contributions, visit the <a href="https://docs.google.com/document/d/1tDo4D7tDabSDR9D8dAPkZcKB88NzyBQDu-Vx4w9gA_M/edit?tab=t.0#heading=h.ttt2y7z4imll" target="_blank" rel="noopener">Full Proposal:&nbsp;Community Engagement and Feedback</a> section.</p>
<p>&nbsp;</p>
<h1 id="budget"><strong>Budget</strong></h1>
<p>For detailed budgetting, visit the <a href="https://docs.google.com/document/d/1tDo4D7tDabSDR9D8dAPkZcKB88NzyBQDu-Vx4w9gA_M/edit?tab=t.0#heading=h.6w6sfpazii0k" target="_blank" rel="noopener">Full Proposal: Budget</a> section.</p>
<p>&nbsp;</p>
<h1 id="conclusion"><strong>Conclusion</strong></h1>
<p>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:</p>
<ol>
<li>Support critical network upgrades as they roll out, like reduced unbonding times and Plaza integration</li>
<li>Improve staking accessibility with streamlined UI and multi-language features</li>
<li>Implement new pool creation and destroying mechanisms for better user control</li>
<li>Further roll out Staking API to turbo charge dashboard speed and reliability.</li>
</ol>
<p>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.</p>
<p>We invite the community to support this proposal and help us continue making staking more accessible to all Polkadot users.</p>
<p>Questions? Comments? Give us your feedback below!</p>
<p>Kind Regards,</p>
<p>Ross Bulat &amp; Joel Kenny</p>

Polkadot Staking Dashboard 2025 (Q1-Q2) Funding Proposal

Treasury

Propose and approve a spend of treasury funds.

## Dispatch Origin

Must be [`Config::SpendOrigin`] with the `Success` value being at least
`amount` of `asset_kind` in the native asset. The amount of `asset_kind` is converted
for assertion using the [`Config::BalanceConverter`].

## Details

Create an approved spend for transferring a specific `amount` of `asset_kind` to a
designated beneficiary. The spend must be claimed using the `payout` dispatchable within
the [`Config::PayoutPeriod`].

### Parameters
- `asset_kind`: An indicator of the specific asset class to be spent.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The beneficiary of the spend.
- `valid_from`: The block number from which the spend can be claimed. It can refer to
  the past if the resulting spend has not yet expired according to the
  [`Config::PayoutPeriod`]. If `None`, the spend can be claimed immediately after
  approval.

## Events

Emits [`Event::AssetSpendApproved`] if successful.

- **Problem Statement & Audience:** Proposal to enhance the Polkadot Staking Dashboard for Q1-Q2 2025, targeting Polkadot users and stakeholders.
- **Significance:** Vital for network security, smoother transitions during upgrades, and global accessibility.
- **Proposed Solution:** Enhancements include easier staking, better rewards tracking, mobile-friendly updates, expanded language support, faster loading times, and improved security.
- **Expected Outcomes:** Improved user experience, enhanced network security, and streamlined staking processes.

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

No Active Proposals