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](https://github.com/polkadot-cloud/polkadot-staking-dashboard/issues/3074) to ask (politely) about this dependency, but the issue was deleted rather than answered.

Could **[@Ross and Joel | Polkadot Cloud](/user/13MNarAqpNkginnQb6gTNq2QnieZGs2SKu8JdK9LLxo6ksEP)** 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](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.

Dear Proposer,

Thank you for your proposal. Our **first** vote on this proposal is **ABSTAIN**. Below is the evaluation of our [voting policy v0.3](https://docs.permanence.io/voting_policy/voting_policy_v0.3.html) on this referendum:

```
MEDIUM SPENDER
--------------
8 available members
🟢 2 • 🔴 0 • ⚪️ 2
✓ ≥50.0% required participation met
✘ Ayes ≤50.0% of all votes
▶ Ayes and abstains are >50.0% of all votes
⚪ ABSTAIN
```

Below is a summary of our members' comments:

> The comments reflected mixed positions regarding the proposal for a staking dashboard. Some members recognized its useful role in supporting staking users and noted that the requested budget was reasonable for six months of work by experienced developers. They supported the proposal for its strategic relevance and timely maintenance of staking tools, even with a reduced budget. Other members, however, expressed reservations, citing their limited use of staking interfaces and concerns over imminent changes in staking and validator systems. They worried that a comprehensive overhaul might be necessary soon, which left them cautious about fully endorsing the proposal.

The full discussion can be found in our [internal voting](https://voting.opensquare.io/space/permanence/proposal/Qmdq88Fue1pbNsGN2MVwUf5XRbXEXJSBKvvu7NUrjcYMGY).

Please feel free to contact us through the links below for further discussion.

Kind regards, Permanence DAO Decentralized Voices Cohort V Delegate 📅 [Book Office Hours](https://cal.com/permanencedao/office-hours) 💬 [Public Telegram](https://t.me/permanencedao) 🌐️ [Web](https://permanence.io) 🐦 [Twitter](https://twitter.com/permanencedao) 🗳️ [Delegate](https://polkadot.subsquare.io/user/15ubZj6T7NUYyQw6j4XBkEMJ2vew5w9kqKEcN1QG7Z1weKDV/votes)

# Milestone 1 Progress Report — February 2026

**Period:** February 2026  
**Repository:** `polkadot-cloud/polkadot-staking-dashboard`

---

## Deliverable Status

### 1) Established collaboration channel with Parity teams
Liaised with W3F and Parity to establish the most effective communication channel for discussing protocol developments and dashboard alignment. W3F have confirmed they are working to identify a point of contact on the Parity side and will update us once allocated. We continue to follow up and remain ready to engage as soon as a direct channel is in place. This deliverable is dependent on external coordination and we have taken all reasonable steps to progress it.

### 2) Continued hosting and support operations
Dashboard remains fully operational at `staking.polkadot.cloud` with **99%+ uptime** throughout February. We also enhanced the `polkadot.cloud` homepage appearance and content for a more seamless staking onboarding experience.

### 3) Discord & email support
Continued responding to user support queries via Discord and email within the SLA. Additionally improved Discord server security measures to better protect the community.

### 4) Transaction signing UI
Comprehensive transaction submission UI redesign has been completed, unifying submission components across all form factors (canvas, full screen, modals, and cards) with context-specific submission text and embedded fee display. Signer-specific logic has been extracted into dedicated hooks behind a unified `useSignerSubmit` facade, reducing duplication across signing flows. A new `ModalBack` component standardises multi-step navigation, and a stacked layout option has been added for constrained contexts such as **Join Pool**.

- **PR #3291** — `feat(ux): Transaction submission UI redesign` (**36dbad7**)

### 5) Paseo testnet integration commenced
Paseo testnet support has been added to both the dashboard and Staking API, addressing Westend RPC instability:

- **PR #3237** — `feat: Add Paseo testnet support` (**6f8254b**)

### 6) Light-client-first connection architecture
Significant groundwork has been completed, including a dedicated smoldot testing package for transaction verification:

- **PR #3244** — `feat(test): Add test-smoldot package for transaction testing` (**f16a5e1**)  
- **PR #3245** — `Fix: test-smoldot initialisation` (**e5118cf**)

Progress on full light-client-first deployment has been temporarily impacted by an external issue in the smoldot library (**smoldot #2198**) which is causing wider ecosystem connectivity problems, not limited to our implementation. We are actively liaising with the Dedot team to explore solutions and workarounds. This is an external dependency and not a blocker on our side.

---

## Additional Work Delivered in February

Beyond the core deliverables, **65 commits** landed on `main` in February across features, fixes, and maintenance:

### Localisation Expansion (3 new languages)
- **PR #3262** — `feat(locale): Add German (Deutsch) language support`  
- **PR #3263** — `feat(locale): Add Korean (한국어) language support`  
- **PR #3272** — `feat(locale): Add Portuguese (Português) language support`  
- **PR #3288** — `feat(ux): Font overrides on per-language basis`  
- **PR #3267** — `Add CLI for locale key translation with LLM integration` — Internal tooling to accelerate future translation work

### Staking Feature Enhancements
- **PR #3265** — `feat(dual-staking): Re-enable dual staking (nominator + pool member)`  
- **PR #3264** — `feat(nominations): Add Favorite Validators button to Manage Nominations`  
- **PR #3268** — `feat: Allow groups of Ledger addresses, multi-device support`

### Codebase Modularisation
- **PR #3246** — `feat(refactor): Modularise page sections into reusable components` — Lays the groundwork for the transaction UI redesign and future Simple Mode improvements

### Bug Fixes
- **PR #3287** — `fix: resolve proxy account source mismatch preventing delegate signing`  
- **PR #3273** — `fix: Show correct stake amount per validator in nomination status`  
- **PR #3249** — `fix: correct Ledger hardware handling bugs`  
- **PR #3250** — `feat(fix): Fix reward trend API`

### UX & Theme Improvements
- **PR #3235** — `Remove pink tint from dark theme, replace with neutral grays`  
- **PR #3236** — `Draw down secondary theme color`  
- **PR #3243** — `DOT icon update`  
- **PR #3253** — `Header menu adjustments`  
- **PR #3254** — `Halving step graph adjustments`

### Dependency Maintenance
**20+ dependency updates** merged, covering React, Dedot chaintypes, Biome, Vite, i18next, Apollo, Stylelint, and more (**#3238–#3242, #3255–#3260, #3274–#3286**).

---

## Summary
All Month 1 deliverables are on track or completed. **65 commits** landed across features, bug fixes, localisation, and maintenance, significantly exceeding the baseline scope. The Parity collaboration channel and light-client-first architecture remain dependent on external parties, but all reasonable steps have been taken on our end to progress these.

# Milestone 2 Progress Report - March 2026

**Period:** March 2026  
**Repository:** `polkadot-cloud/polkadot-staking-dashboard`

## Deliverable Status

### 7. Continued dependency updates

Weekly dependency updates have been maintained throughout March, with **67 dependency update commits** landing on `main`, continuing the high-cadence maintenance established in previous periods.

Notable major version upgrades include:

- **TypeScript** `5.9.3 → 6.0.2` (#3373)
- **Vite** `7.3.1 → 8.0.0 → 8.0.2` (#3347, #3367)
- **@tanstack/react-query** `5.90.21 → 5.95.2` (#3371)
- **i18next** `25.8.13 → 25.10.5` (#3334, #3352, #3372)
- **bignumber.js** `9.3.1 → 10.0.2` (#3309)
- **@biomejs/biome** `2.4.4 → 2.4.8` (#3302, #3328, #3343, #3364)
- **stylelint** `17.3.0 → 17.5.0` (#3308, #3374)
- **vitest** `4.0.18 → 4.1.1` (#3349, #3369)
- **CI: pnpm/action-setup** `4 → 5` (#3363)

Additionally, Polkadot ecosystem dependencies (`@dedot/chaintypes`) were bumped across multiple updates (#3304, #3331, #3348, #3368) to maintain compatibility with the latest chain types.

### 8. Bug fixes & reliability improvements

Several targeted bug fixes and reliability improvements were delivered:

- **PR #3327** - fix: stale closure in Tooltip mousemove handler
- **PR #3326** - fix: event listener leak in ThemesProvider
- **PR #3338** - fix: fetch all pages of `erasStakersPaged` for nomination status
- **PR #3314** - fix: correct typos
- **PR #3313** - fix: localise hardcoded string and remove `console.error` in validator search
- **PR #3341** - chore: add UTC safeguards for time calculations

In addition, a dedicated performance pass was undertaken with **8 optimisation commits**, including:

- **PR #3359** - perf: stabilise handler refs and memoize context values in UI overlay providers
- **PR #3358** - perf: memoize `FiltersContext` value and stabilise handler refs
- **PR #3357** - perf: stabilise `wrappedPoolSearchFilter` reference with `useCallback`
- **PR #3356** - optimise: use `Set` for `eraValidators` membership lookup in `useValidatorFilters`
- **PR #3322** - chore: optimise validator list performance lookup
- **PR #3320** - perf: remove redundant null fallback in duration helper
- **PR #3318** - chore: optimise token price formatter
- **PR #3317** - chore: optimise era high calculation in current era graph

These optimisations collectively reduce unnecessary re-renders, stabilise callback references, and improve lookup performance across the validator and pool filtering systems.

### 9. Ledger Flex & Stax support

Full support for **Ledger Flex** and **Ledger Stax** devices has been implemented and merged, compatible with firmware versions current as of **February 2026**.

The implementation includes:

- **Device type detection and classification:** A `LedgerDeviceModel` type system distinguishing between `nano_s`, `nano_x`, `nano_s_plus`, `flex`, `stax`, and `unknown` models, with a `LedgerDeviceFamily` grouping (`nano` vs `touchscreen`)
- **Per-device icons:** WebP device renders for Nano, Flex, and Stax for intuitive device identification in the UI
- **Per-device submission instructions:** Device-aware signing prompts that adapt to the specific device in use (for example, touchscreen vs button-based interaction guidance)
- **Per-device error messages:** Replaces generic "Ledger device" messages with specific device names (for example, "Connect your Ledger Flex to continue"), with translations across all 6 supported languages
- **Device model persistence:** Detected device model is persisted to `localStorage`, maintaining device awareness across page refreshes with zero performance impact for non-Ledger users
- **Unified type system:** Ledger device types have been centralised in the shared types package for cross-package reusability

### 10. Codebase modularisation

Modularisation work continued in March, building on the foundation laid in February:

- **PR #3342** - refactor: extract reusable `WarningPrompt`, `NominationsEmpty` & `AnnouncementsList` components
- **PR #3316** - feat(refactor): add era arg to `getNomineesStatus` for more flexible nomination status queries
- **PR #3375** - feat(refactor): optimise Vite React plugin configuration

These extractions continue to reduce duplication and enable consistent rendering across Advanced and Simple Mode.

## Additional Work Delivered in March

Beyond the core deliverables, **142 commits** landed on `main` in March across features, fixes, performance, theming, and maintenance.

### Visual & Theming Redesign

A comprehensive theming refactor was completed, introducing a modern and cohesive visual system:

- Introduced grayscale CSS variable system (`--gray-x`, `--shade-x`) replacing legacy accent variables
- Removed legacy variables:
  - `--accent-primary`
  - `--accent-secondary`
  - `--accent-tertiary`
  - `--accent-stroke`
  - `--accent-pending`
  - `--accent-transparent`
- Per-network accent shading for distinct visual identity across **Polkadot / Kusama / Westend / Paseo**
- Font redesign:
  - **Inter → DM Sans** for body text
  - **DM Serif Display** for titles
  - **JetBrains Mono** for stats
- Updated favicon and token icon styling
- Rebalanced dark mode for improved readability

Related PR:

- **PR #3325** - feat(ux): lighten background, amend card shadow

### New Features

- **PR #3360** - feat: add Account Sync QR - allows users to sync accounts via QR code
- **PR #3290** - feat: improved pool & validator sharing functionality

### Ecosystem Updates

- **PR #3337** - chore: remove Mimir wallet option following sunset announcement

### Housekeeping

- **PR #3301** - chore: update copyright headers from 2025 to 2026

## Summary

All Month 2 deliverables have been completed.

**142 commits** landed across dependency updates, bug fixes, performance optimisations, Ledger hardware support, codebase modularisation, and a comprehensive theming redesign, significantly exceeding baseline scope.

Weekly dependency updates were maintained at a high cadence with **67 updates**, including major version upgrades to **TypeScript 6**, **Vite 8**, and other core tooling.

The Ledger Flex and Stax integration delivers a polished, device-aware hardware wallet experience across all supported languages.

# Milestone 3 Progress Report - April 2026

**Period:** April 2026  
**Primary repository:** `polkadot-cloud/polkadot-staking-dashboard`  
**Supporting repositories:** `polkadot-cloud/staking-docs`, `polkadot-cloud/connect`, `polkadot-cloud/app` (Staking Companion), Polkadot Cloud landing page

## Deliverable Status

### 11. Continued Protocol Collaboration

We have had brief preliminary contact with Parity, but as much of the upcoming protocol work has been kept under wraps internally. We continue to track relevant Polkadot Forum announcements, runtime upgrades, and ecosystem signal, and remain ready to engage substantively as soon as a direct contact is allocated and discussion can be productive.

The smoldot 2.0.40 to 3.1.1 upgrade landed in April (PR #3441, PR #3459), giving us forward compatibility ahead of further light-client-first deployment work.

This deliverable is dependent on external coordination and we have taken all reasonable steps to progress it.

### 12. Essential Maintenance Continuation

Hosting, support, and dependency cadence were all maintained at the previous milestone's level:

- **Hosting:** `staking.polkadot.cloud` remained fully operational with 99%+ uptime through April.
- **Support:** Discord and email queries continued to be handled within the 24 hour SLA.
- **Dependency updates:** approximately 40 dependency and CI update PRs landed on the dashboard in April, plus 14 on the docs portal. Notable major bumps include:
  - smoldot 2.0.40 to 3.1.1 (PR #3441, PR #3459)
  - bignumber.js 10.0.2 to 11.0.0 (PR #3447)
  - TypeScript 6.0.2 to 6.0.3 (PR #3444)
  - Vite 8.0.3 to 8.0.10 (PR #3401, PR #3417, PR #3439, PR #3453)
  - `@tanstack/react-query` 5.95.2 to 5.100.5 (PR #3403, PR #3427, PR #3448, PR #3460)
  - i18next 25.10.9 to 26.0.8 (PR #3389, PR #3421, PR #3446, PR #3461)
  - react-i18next 16.6.6 to 17.0.1 (PR #3381)
  - `@vitejs/plugin-react` 5.2.0 to 6.0.1 (PR #3386)
  - `@dedot/chaintypes` 0.249.0 to 0.263.0 (PR #3402, PR #3418, PR #3440)
  - `@apollo/client` 4.1.7 to 4.1.9 (PR #3457)
  - Plus ongoing Biome, stylelint, prettier, sass, vitest, postcss, dotenv, openai, and grouped React updates throughout the month.
- **CI tooling:**
  - PR #3413 bump pnpm/action-setup 5 to 6
  - PR #3412 bump actions/upload-pages-artifact 4 to 5
  - PR #3450 bump googleapis/release-please-action 4 to 5
  - PR #3378 bump actions/configure-pages 5 to 6
  - PR #3379 and PR #3436 bump dependabot/fetch-metadata 2.5.0 to 3.1.0
- **Bug fixes and reliability:**
  - PR #3434 fix(Invite): strip duplicate https:// prefix and improve icon contrast
  - PR #3377 fix: remove unused dep, hardcoded variable, alt text
  - PR #3393 perf: stable callbacks and memoised lookups in useValidatorFilters
  - PR #3432 feat(refactor): use stable identifiers as React keys for list rendering

### 13. Visual Progress Tracker for Unbonding

Delivered and merged: PR #3292 feat(ux): Visual progress tracker for unbonding chunks.

The implementation includes:

- New reusable `ProgressBar` component at `packages/app/src/library/ProgressBar/`, integrated into the `UnlockChunks` modal across both the chunks list and the overview view.
- **Sub-era interpolation:** progress advances smoothly within the current era rather than jumping between eras.
- **Chain-constant driven:** the calculation reads the unbonding period from chain constants, so the tracker works with the current 28 day unbonding period and will continue to work unchanged with future 1 day unbonding.
- **Active vs complete states:** active chunks render an animated gradient with a subtle shimmer; unlocked chunks render a clear "ready to withdraw" state.
- **Accessibility:** progress values are announced via ARIA labels, with a dedicated "ready to withdraw" announcement when a chunk completes, in place of the less meaningful "100%".
- **Reduced motion:** respects `prefers-reduced-motion`, suppressing shimmer animation for users who have opted out.
- **Performance:** a single shared 60 second ticker is used across the overview, avoiding multiple independent timers when many chunks are present.
- **Localisation:** new copy translated across all 6 supported dashboard languages: EN, DE, ES, KO, PT, ZH.

### 14. Documentation Portal: Usage Guides Onboarded

The docs portal at `docs.staking.polkadot.cloud` went from 3 reference pages in 3 languages (Welcome, Glossary, FAQ) to 15 pages with full coverage in 5 languages, growing from 9 documents live to roughly 70 documents live in a single month.

Seven full usage guides were authored, translated, and shipped:

| Guide | PR | Languages | Simple / Advanced |
|---|---:|---|---|
| Getting Started | #135 | en, es, zh, pt, ko | Both (toggle via `?advanced`) |
| Solo Nominating | #136 | en, es, zh, pt, ko | Both |
| Nomination Pools | #142 | en, es, zh, pt, ko | Both |
| Rewards and Payouts | #143 | en, es, zh, pt, ko | Single |
| Unbonding and Withdrawals | #144 | en, es, zh, pt, ko | Single |
| Exploring Validators | #145 | en, es, zh, pt, ko | Single (Advanced-only feature) |
| Support and Resources | #147 | en, es, zh, pt, ko | Single |

Simple / Advanced toggle infrastructure was activated via PR #146: the framework now reads `hasAdvanced: true` from MDX frontmatter and exposes a tab toggle on the three guides where Advanced flows materially differ.

**Language expansion:** Portuguese, Korean, and German were added to the portal (PR #132), with the dropdown fix in PR #133 rendering each language in its native name. Portuguese and Korean reached full content parity with English and Spanish across the new April content set. German content remains at Welcome / FAQ / Glossary, and translation of the new guides into German is planned for May.

**Editorial pass:** a portal-wide pass enforced punctuation rules (no em dash or double hyphen), restructured sentences with clearer connectors, added "Next Steps" cross-links to every guide, and aligned April publication dates.

Continued additions and refinements are expected through May as further usage flows come online, for example, deeper Pool Admin coverage and the new mobile companion onboarding.

### 15. Network Onboarding Documentation and Support Flow

A dedicated Developer section is now live on the docs portal. PR #134 shipped two pages covering all five sub-deliverables of Task 15:

| Sub-deliverable | Status | Where |
|---|---|---|
| Light client specs onboarding | Live | Network Integration (smoldot / `@dedot/chain-specs` step) |
| Dedot service implementation guide | Live | Developer Overview + Network Integration |
| Staking API onboarding | Live | Developer Overview + Network Integration (Staking API verification step) |
| Network icons and theming docs | Live | Network Integration (SVG asset registration + HSL accent-color theming) |
| Support channel surfacing | Live | Support and Resources page (PR #147) |

A network integrator can now follow a 9-step onboarding checklist covering type registration, network config, Dedot service implementation, smoldot integration, SVG and accent theming, Staking API verification, and final smoke testing, without having to read dashboard source code.

On the dashboard side, the addition of the DeServe RPC provider for Polkadot Asset Hub (PR #3391) serves as a concrete worked example of an endpoint addition flow, alongside the ongoing `@dedot/chaintypes` updates that keep multi-network type support current.

With upcoming protocol changes landing in May, this section will continue to be expanded with additional integrator guidance and worked examples.

## Additional Work Delivered in April

Beyond the core deliverables, this milestone saw substantial new product and architecture work across the Polkadot Cloud ecosystem.

### Staking Companion: Native iOS and Android App Launched

A new native mobile companion app was built and brought to release-candidate state in this period at `github.com/polkadot-cloud/app`.

**What it is:** Staking Companion is a native iOS and Android app that lets Polkadot stakers track and manage their staking positions on the go. Accounts are paired from `staking.polkadot.cloud` via QR code (no private keys ever touch the phone), and the app surfaces real-time balances, validator nominations, reward history, pool participation, and chain status using direct RPC queries via Polkadart and the Polkadot Cloud GraphQL Staking API.

**Launch feature set:**

- Watch any Polkadot account on mobile via QR pairing from the Staking Dashboard, with multi-account support, account switcher, reorder, and remove.
- Live portfolio at a glance: total balance with USD valuation, free / locked / unlocking breakdown, donut chart of allocation.
- Staking summary: total staked, 30 day rewards with trend, active-staking status, reward trend chart, top active nominations preview.
- Validator nominations browser with status filters, search, and per-validator stats.
- Reward history sourced from the Polkadot Cloud Staking API.
- Configurable RPC endpoint with auto-RPC and manual selection (StakeWorld, DeServe, IBP1, IBP2).
- Biometric app-lock, light / dark / system theme, haptic feedback, automatic recovery from offline / airplane mode.
- Tinted and adaptive launcher icons, native QR scanner via ML Kit / ZXing.

**Integration with the broader stack:** the companion consumes the same Polkadot Cloud GraphQL Staking API that powers the dashboard, and uses the same curated Asset Hub endpoint list. Account pairing is one-way and capped to read-only metadata, with the dashboard remaining the source of truth for any signing operation.

April activity on this repo focused on iOS and Android polish, RPC health indicator, biometric fallback, adaptive dialogs, DOT price card, and adaptive launcher icons across 14 in-flight branches.

### `@polkadot-cloud/connect`: New Modular Wallet Connectivity Toolkit

A new modular wallet connectivity toolkit was published to npm in April, live on `polkadot.cloud/connect`.

**What it is:** a single React provider plus optional adaptors for browser extensions, Ledger hardware wallets, Polkadot Vault (QR-based), and proxy accounts, exposing typed hooks (`useExtensions`, `useExtensionAccounts`, `useImportedAccounts`, `useActiveAccount`, `useProxiesLifecycle`) over the Dedot API layer. Designed to be both a drop-in for human developers and consumable by AI coding agents via shipped skill files.

**Timeline:** first commit 2026-04-16; first npm publish 2026-04-17; adopted by the Staking Dashboard via PR #3433 on 2026-04-18, one day after publication.

**Packages published:**

| Package | npm version | Role |
|---|---:|---|
| `@polkadot-cloud/connect-core` | 1.0.9 | Core observables for extension and account discovery (no React) |
| `@polkadot-cloud/connect` | 1.0.9 | React provider and hooks |
| `@polkadot-cloud/connect-ledger` | 1.0.2 | Ledger hardware wallet adaptor |
| `@polkadot-cloud/connect-vault` | 1.0.2 | Polkadot Vault (QR) adaptor |
| `@polkadot-cloud/connect-proxies` | 0.2.3 | Proxy account adaptor and lifecycle hooks |

**Why this extraction matters:**

- **Modularity:** the dashboard's wallet code is now a versioned external dependency, reusable by any Polkadot dapp.
- **Ecosystem reuse:** all packages are on npm under `@polkadot-cloud/*`, making third-party adoption frictionless.
- **Type safety and ergonomics:** Dedot-typed APIs, with a registry pattern that makes multi-network apps materially cleaner.
- **Agent-ready:** shipped skill files in `.agents/skills/` give AI coding tools structured integration procedures, making Connect one of the first Polkadot dev libraries with first-class agent documentation.

### Dashboard Architecture and Feature Work

Beyond the deliverables, the dashboard saw substantial refactor and feature work in April:

- PR #3435 feat(refactor): Pool commission management UX redesign
- PR #3433 feat(refactor): use `@polkadot-cloud/connect`
- PR #3449 feat(refactor): Abstract proxy account support
- PR #3430 feat(refactor): Separate active proxy context
- PR #3409 feat: Use latest connect kit
- PR #3407 feat(refactor): Proxy hardware accounts hook, refactor connect package conventions
- PR #3398 Separate all vault logic into standalone vault-connect package
- PR #3395 Separate all ledger logic into standalone ledger-connect package
- `styled` to `ui-styles` internal migration, consolidating styling primitives

### Polkadot.Cloud Landing Page

The landing page at `polkadot.cloud` received editorial and structural work to surface the broader ecosystem, with 16 commits across 5 PRs.

The landing page now surfaces all three primary properties: the Staking Dashboard, the Staking Companion app, and Polkadot Connect.

### Polkadot Cloud GraphQL Staking API

36 commits landed on the supporting API in April, including a new `sendEmail` mutation, anti-spam measures and validation logic, path / basePath cleanup, bigint type fixes, and ongoing dependency maintenance (Prisma 7.5.0 to 7.7.0, Apollo, Resend, Cloudflare Workers types, `@dedot/chaintypes`).

This API now powers both the Staking Dashboard and the new Staking Companion mobile app.

## Summary

All Month 3 deliverables have been completed.

The visual unbonding progress tracker is merged and live with sub-era interpolation and translations across 6 languages, future-proofed against the upcoming 1 day unbonding period.

The documentation portal grew from 9 to roughly 70 live documents in a single month, with 7 full usage guides shipped in 5 languages and a brand new Developer / Network Onboarding section that covers all five sub-deliverables of Task 15. Continued additions are expected through May, including translating the April content set into German.

Beyond the deliverables, this milestone saw the launch of two new ecosystem products: the native iOS and Android Staking Companion mobile app (read-only, paired by QR from the dashboard), and the modular `@polkadot-cloud/connect` wallet connectivity toolkit, now published to npm and adopted by the dashboard within a day of release.

Weekly dependency updates were maintained at a high cadence, with notable major upgrades to smoldot 3, bignumber.js 11, TypeScript 6.0.3, and Vite 8.0.10.

Hosting and 24 hour support response times were maintained throughout.

# Milestone 4 Progress Report - May 2026

**Period:** May 2026
**Primary repository:** `polkadot-cloud/polkadot-staking-dashboard`
**Supporting work across:** Polkadot Staking API, Staking Companion iOS and Android, staking-docs portal, `@polkadot-cloud/connect`, `polkadot.cloud`

## Deliverable Status

### 16. Contingency Capacity for Protocol Adaptations

No protocol-level activations reached deployment stage during May. OpenGov Referendum 1890, which sets `MinValidatorBond` to 10,000 DOT, is in its decision period with strong Aye support and represents the mandatory prerequisite for the subsequent nominator-unslashable and fast-unbonding protocol changes.

We are actively tracking the referendum and ecosystem signal so we can move quickly once it enacts and the follow-on changes are scheduled.

Per the deliverable wording, reserved capacity has been redirected to backlog items spanning UI polish, performance work, documentation improvements, and product expansion. This redirected capacity directly produced:

* Pool rewards analytics expansion
* Pool shares chart
* Enhanced rewards list pagination
* Lazy-load architecture work for Advanced Mode pages
* Performance optimisation passes across nomination filtering, extension filtering, and payout rendering
* German language parity in the documentation portal
* May Staking Companion release

### 17. 1-Day Unbonding Support

The interface and code infrastructure for 1-day unbonding is shipped and production-ready pending protocol activation.

* The visual unbonding progress tracker shipped in April via PR `#3292`.
* The tracker reads the unbonding period directly from chain constants.
* When the 1-day unbonding upgrade activates on Polkadot Asset Hub, no further engineering work is required.
* The tracker will continue to function unchanged, simply rendering a much shorter countdown.
* The underlying time calculations, including `useEraTimeLeft` and chunk progress logic, are network-agnostic and chain-constant driven.
* The same code path already handles Westend, Paseo, and Kusama with their respective unbonding periods.
* The Polkadot 28-day to 1-day transition is therefore a protocol-level configuration change rather than a dashboard code change.
* Deployment procedure is documented internally. On protocol activation, no release is required from our side.
* Verification will be handled through the existing monitoring on `staking.polkadot.cloud`.

### 18. Staking Reward Predictions

Predictive reward analytics shipped across both the Staking API and the dashboard in May, using historical reward data to surface forward-looking signal directly inside the existing reward charts.

#### Staking API Work

The pool rewards subsystem was substantially expanded to support per-pool-member era reward analysis. New capabilities include:

* Pool member per-era rewards
* Combined reward and pool-share query
* Share-timestamp tracking for accurate share-weighted calculations
* Configurable reward depth for adjustable historical windows
* Reward pagination for large datasets
* Corrected pool share calculation to improve prediction accuracy

#### Dashboard Work

The rewards charts now visualise the expanded data through the following updates:

* **PR `#3498` - Pool shares chart**
 Adds a dedicated visualisation of pool share evolution over time, surfacing the share-weighted distribution that drives reward calculation.

* **PR `#3484` - Add pool shares to PayoutBar graphs**
 Existing payout bar graphs now overlay pool shares for richer context on each historical payout.

* **PR `#3497` - Enhanced rewards list pagination**
 The rewards list now scales gracefully for accounts with long reward histories.

* **PR `#3485` - Use generic Staking API functions**
 The reward-display layer was refactored to consume the new generic Staking API surface, decoupling chart components from any one network and positioning them for additional predictive overlays without further refactoring.

### 19. Health Monitoring RPC Endpoints

Task 19 has been delivered. The Polkadot Staking API now exposes a gated RPC health monitoring endpoint that third-party integrators can consume with an issued API key.

Key features include:

* **Per-key rate limiting**
 Each API key is limited to 1,000 requests per hour, enforced at the resolver layer. Over-limit requests return a `TOO_MANY_REQUESTS` GraphQL error.

* **API key infrastructure**
 API keys are SHA-256 hashed and persisted to the database. Keys are never stored in plaintext.

* **Header support**
 Requests support both the primary `x-api-key` header and an `Authorization: Bearer <key>` fallback.

* **Authentication and authorisation responses**
 Unauthenticated requests return `UNAUTHENTICATED`. Unknown or disabled keys return `FORBIDDEN`.

* **Domain allowlist enforcement**
 Each issued key can carry an optional list of allowed domains. When set, the request `Origin` or `Referer` hostname is suffix-matched against the allowlist before the request is authorised. This protects issued keys against use from unintended domains.

* **Documentation**
 Documentation is published at `docs.staking.polkadot.cloud/en/api-token-documentation`, covering request flow, headers, example query, and response shape. It is translated into all six supported languages: English, Spanish, Chinese, German, Portuguese, and Korean.

* **First integrator wired up**
 The Staking Dashboard now consumes the gated endpoint with its own API key via PR `#3513`, serving as the reference implementation.

The endpoint exposes per-network health data including relay chain, staking chain following Asset Hub migration, and People Chain RPC endpoints, with labels and WSS URLs that integrators can route to.

## Additional Work Delivered in May

Beyond the core deliverables, 72 commits landed on the dashboard `main` branch in May, with substantial additional work across supporting repositories.

### Dashboard: Features, Performance, and Architecture

* **PR `#3431` - Lazy-load modals and canvas components**
 Reduces initial bundle size and improves time-to-interactive on first load.

* **PR `#3483` - Lazy-load Advanced Mode pages**
 Extends the lazy-loading pattern to Advanced Mode-only pages, ensuring Simple Mode users do not download advanced bundles.

* **PR `#3289` - Direct users to Unstake when bonded below minimum nominator bond**
 Provides a clearer remediation path when stake falls below the protocol minimum.

* **PR `#3499` - Collapse `find` and `indexOf` passes in payout list rows**
 Removes redundant array passes on every render.

* **PR `#3500` - Use Set lookups for nomination and extension filtering**
 Converts `O(n)` array scans to `O(1)` Set lookups across the validator filtering layer.

* **PR `#3195` - Release main**
 Release Please cut a new versioned release of the dashboard, formalising the May feature set.

### Dashboard: Maintenance and Dependency Hygiene

Weekly dependency updates were maintained at the same cadence as previous milestones, including:

* `smoldot` `3.1.1` to `3.1.3`
* `bignumber.js` `11.0.0` to `11.1.1`
* `@apollo/client` `4.1.9` to `4.2.0`
* `@dedot/chaintypes` `0.269.0` to `0.280.0`
* `@tanstack/react-query` `5.100.5` to `5.100.14`
* `vite` `8.0.10` to `8.0.14`
* `i18next` `26.0.8` to `26.2.0`
* `date-fns` `4.1.0` to `4.3.0`
* Ongoing grouped React, types, Biome, Sass, PostCSS, Prettier, Stylelint, and OpenAI bumps

A Vite minor upgrade introduced a CSS regression mid-month. The issue was caught immediately, all affected dependency PRs were cleanly reverted in a coordinated rollback, the offending Vite version was pinned, and re-application proceeded with stricter pre-merge verification once the fix was confirmed.

This incident demonstrates the release hygiene that keeps the dashboard at 99%+ uptime.

### Hosting and Support

The dashboard remained fully operational at `staking.polkadot.cloud`, with 99%+ uptime maintained throughout May.

Discord and email support queries continued to be handled within the 24-hour SLA.

### Staking Companion: Live on App Store and Google Play

The native iOS and Android Staking Companion is live and in active distribution on both stores. Two further releases shipped in May:

* **v1.0.3 - May 8**
 The DOT price is now displayed on the Overview screen.

* **v1.0.4 - May 9**
 Bug fixes and performance improvements, including QR scanner fixes for Huawei devices and an Android QR output fix.

This brings the Companion to its fourth public release and extends the read-only mobile staking experience first launched in April. The app continues to consume the Polkadot Cloud GraphQL Staking API as its primary data source and remains paired to the dashboard via QR for account onboarding.

### `@polkadot-cloud/connect`: Launch Promotion

Connect, the modular wallet connectivity toolkit launched on npm in April and adopted by the dashboard the same week, received a dedicated long-form launch article on `polkadot.cloud` in May.

The article is live at `polkadot.cloud/blog` and surfaces the project to the broader Polkadot developer ecosystem.

### Polkadot Staking API

51 commits landed on the supporting API in May.

Beyond the API key infrastructure and pool rewards expansion covered under Tasks 18 and 19, ongoing maintenance included:

* Withdraw-destroying-pool-members support
* `pm2` major version upgrade from 5 to 7
* Apollo Server dependency maintenance
* Resend dependency maintenance
* `express-rate-limit` dependency maintenance
* GraphQL dependency maintenance
* Nx dependency maintenance
* Biome dependency hygiene
* CI tooling updates

## Summary

All Month 4 deliverables are completed or in their intended state.

Task 19, the RPC health monitoring API, shipped a gated endpoint with 1,000 requests per hour per-key rate limiting, SHA-256 hashed key infrastructure, domain allowlist protection, documentation translated into six languages, and the dashboard wired up as the first integrator.

Task 18, reward predictions, shipped predictive reward analytics across both the API and dashboard. The Pool shares chart and enhanced PayoutBar visualisations now consume the substantially expanded pool rewards subsystem.

Task 17, 1-day unbonding, is in the production-ready state defined by the deliverable. The visual interface has been live since April, the code is chain-constant driven, and the system is awaiting OpenGov Referendum 1890 to enact `MinValidatorBond` as the protocol prerequisite before the follow-on fast-unbonding referendum is scheduled.

Task 16, contingency capacity, was redirected in line with the deliverable wording into substantive product work documented across this report.

Beyond the core deliverables, 72 dashboard commits drove new features, including the Pool shares chart, Pool shares in PayoutBar, enhanced rewards list pagination, and lazy-loading across modals, canvas, and Advanced Mode pages. Performance optimisations included Set lookups and collapsed array passes. A Release Please cut formalised the May release.

The Staking Companion shipped two further versions in May: v1.0.3 added the DOT price to the Overview screen, and v1.0.4 delivered bug fixes and QR device improvements. Both are live on the App Store and Google Play.

The Polkadot Staking API expanded the pool rewards subsystem across six dedicated work items. Connect received a launch article on `polkadot.cloud`. Hosting, support, and the weekly dependency cadence were maintained throughout.

Every committed Milestone 4 task has been delivered. Reserved capacity was redirected into substantial additional product work, and the team remains ready to move on protocol activations as soon as they enact.

**Proponents**
Ross Bulat and Joel Kenny

**Beneficiary Address**
13MNarAqpNkginnQb6gTNq2QnieZGs2SKu8JdK9LLxo6ksEP

**Track**
Medium Spender

**Requested Amount**
$66,000 USDC

**Funding Period**
6 months (February 2026 – July 2026)

**IPFS Link**
https://bafybeic7xzt4y2g6hwrma2h2ysmq4jcw2iuhxc7ablscebdanbcg4aph24.ipfs.dweb.link?filename=%5BPUBLIC%5D%20Polkadot%20Staking%20Dashboard_%20Protocol-Aligned%20Development.pdf

We present a revised proposal for the Polkadot Staking Dashboard, demonstrating fiscal responsibility and strategic focus based on community feedback. 

This proposal delivers protocol-aligned maintenance - sustaining the reference staking implementation while maintaining readiness to adapt to critical protocol changes including DAP, 1-day unbonding, and other staking system evolution.

**Full proposal details on Google Docs:** https://docs.google.com/document/d/1IwbdBg3SesJpszE1I5jsWUvSCNseK1UvpP-j_zYu1C0/edit?usp=sharing

- **Who:** Ross Bulat and Joel Kenny are working on this project.
- **What:** They want to build a Polkadot Staking Dashboard.
- **Goal:** To help people understand and use the Polkadot staking system.
- **How Much:** They are asking for $66,000.
- **How Long:** The project will last for 6 months.
- **Why:** To keep the dashboard updated and ready for new changes in Polkadot.
- **Where:** More details are in their online document.

#212·Polkadot Staking Dashboard: Protocol-Aligned Development