Notice: Polkadot has migrated to AssetHub. Balances, data, referenda, and other on-chain activity has moved to AssetHub.Learn more
Advancing OpenGov's Core: Governance Enhancements & Automated Analytics, Cost Optimization, and Infrastructure Expansion – Retroactive Funding Request
TL;DR
This proposal asks the Polkadot Treasury to retroactively fund transparency and infrastructure work that keeps OpenGov usable after the Asset Hub migration and aligns with the 2025 Social Contract (Ref. 1463).
Scope is limited to:
- Transparency & analytics: Treasury, delegation, bounty and judgement dashboards
- Identity & relationships: identity flows, judgements, proxies and account mapping
- Core infrastructure: multi-chain indexer (Relay + Asset Hub), GCP migration and PAPI integration
- Developer support: reusable components and APIs that other teams already build on
Proposal scope & budget on IPFS: IPFS Doc
Proposal detail & budget sheet: Polkassembly Q4 2025
What this proposal funds
A. Transparency & analytics
All work here is either live or scheduled for completion by mid–Dec 2025:
- Judgement Explorer: registrar activity, fees, turnaround times in one place
- Coretime & Spends dashboard (by 15 Dec): balances, inflows/outflows, efficiency trends
- Treasury Analytics (by 15 Dec): balances, liabilities, model-based spend categorisation, plus reporting aligned with opengov.watch and recent Alice_und_Bob work
- Delegation statistics (by 20 Dec): delegation flows and voting behaviour
- Bounty analytics (by 20 Dec): completion rates, curator performance, ROI by category
B. Identity & verification infrastructure
- Sub-identity flow: simplified UX for creating and managing sub-identities
- Account relationships (by 20 Dec): mapping between accounts, proxies and multisigs
- Proxy Explorer: unified dashboard for governance, staking and identity proxies
C. Technical upgrades – Asset Hub + infra
To support the Asset Hub migration and reduce long-term infra risk/costs, we delivered:
- A unified multi-chain indexer (Relay + Asset Hub) with historical continuity
- Refactored Next.js frontend, APIs, caching and schema to be chain-aware
- Migration to GCP with Cloud Run, CI/CD pipelines, global load balancing and Secret Manager
- PAPI.how integration to stabilise multi-chain RPC and reduce ops overhead
Measured impact so far:
- Page load times reduced by ~60%
- API response times reduced by ~35%
- Projected infra and maintenance savings: >150k USD next year, >400k USD over three years based on current usage and costs
D. Developer infrastructure
- Public, multi-network API layer (Polkadot, Kusama, Moonbeam, Moonriver)
- Reusable UI components, hooks, wallet-connect helpers and governance widgets
- NPM packages and usage guides so parachains and products can integrate OpenGov data without rebuilding their own backend
Scope exclusions and no-overlap commitment
- No AI funding: Klara, DelegateX and AI forecasting are not part of this ask. They will be discussed separately with the Foundation, Parity and the community.
- No Fellowship workflows: All Fellowship-specific UX and process work has been removed from scope.
- No overlap with Ref. 1463 maintenance: This proposal covers new infra and feature work, not baseline maintenance already funded in the 2025 Social Contract.
We look forward to useful feedback for the direction ahead. If you have any questions, please drop them in the comments here on Polkassembly, or on our Telegram and X.
Comments (1)
Comments are restricted to accounts with an on-chain verified identity.


We have received a few recurring questions around scope, retroactivity, overlap with Ref. 1463, Asset Hub migration work and the removal of AI features from this request. To make review easier, we have prepared a full FAQ that explains:
You can read the full FAQ and detailed breakdown here:**** FAQ****
We will continue to add clarifications based on reviewer and community feedback.