## TL;DR

DotPulse is an open-source dashboard that maps Polkadot's **full infrastructure stack** across 10 critical categories — Protocol Development, Contract & Token Standards, Wallets, Oracles, Bridges, On/Off-ramps, Relayers, Explorers, Indexers, and Data Lakes — while simultaneously aggregating ecosystem-wide metrics (TVL, active users, transactions, XCM activity) into a single unified view.

Think of it as **L2Beat meets Electric Capital's Developer Report**, purpose-built for Polkadot.

The problem is straightforward: no one — not investors, not developers, not even community members — can currently see the full picture of Polkadot's infrastructure maturity and ecosystem health in one place. DefiLlama fragments parachains into separate entries. DappRadar treats each chain independently. Infrastructure tooling (wallets, oracles, bridges, indexers) has no comparative mapping. DotPulse fixes this.

---

## The Problem

### 1. Ecosystem Metrics Are Fragmented

When someone looks up Polkadot on DefiLlama, they see Hydration at ~$55M TVL, Bifrost and Moonbeam listed separately — not a combined ecosystem with ~$300M+ in DeFi TVL and ~$400M in total ecosystem value. Meanwhile, Cosmos, Avalanche, and Solana all present unified numbers. This fragmentation has been discussed on the Polkadot Forum since 2023, but no purpose-built public solution exists.

The Tie launched a Polkadot Ecosystem Dashboard in September 2024, but it sits behind an institutional paywall. The community needs a **free, open-source, publicly accessible** equivalent.

### 2. Infrastructure Coverage Has No Single Map

Polkadot's infrastructure landscape has evolved dramatically — Polkadot Hub launched smart contracts in January 2026 with dual VM support (REVM + PolkaVM), Snowbridge V2 went live with sub-$1 fees, Hyperbridge crossed $300M in transaction volume, and Acurast is building a 100K+ device oracle network. Yet there's no dashboard where a developer, investor, or community member can see:

- Which wallets support which parachains? - What oracle solutions are actually live and feeding data? - How do Polkadot's bridges compare on TVL, fees, and supported routes? - Where are the infrastructure gaps that still need filling?

Ethereum has [L2Beat](https://l2beat.com) for rollup infrastructure comparison. Polkadot has nothing comparable.

### 3. The Narrative Cost Is Real

When institutional researchers or crypto media evaluate ecosystems, they use dashboards and aggregated data. Without unified metrics, Polkadot consistently appears smaller than it is. This directly impacts DOT perception, capital inflows, and developer interest. The March 2026 inflation cut (53% reduction in issuance) makes it even more critical to maximize narrative impact per treasury dollar spent.

---

## The Solution: DotPulse

DotPulse is a free, open-source web application organized around **two core pillars**:

### Pillar 1: Infrastructure Map (10 Categories)

Each category gets a dedicated module tracking the current state of tooling in the Polkadot ecosystem:

| # | Category | What DotPulse Tracks | Key Polkadot Projects Covered | |---|----------|---------------------|-------------------------------| | 1 | **Protocol Development** | Runtime versions, SDK releases, RFC status, Polkadot Hub contract deployments, PolkaVM/REVM adoption, JAM development progress | Parity, Fellowship, Polkadot SDK | | 2 | **Contract & Token Standards** | Deployed standards, library availability, verified contracts, XC-20 assets, PSP token standards, OpenZeppelin coverage | OpenZeppelin (Hub support), XC-20, ERC-20/721/1155 on Hub | | 3 | **Wallets** | Wallet ecosystem map with parachain support matrix, hardware wallet coverage, social login availability, XCM integration depth | Nova Wallet, Talisman, SubWallet, Polkadot Vault, Ledger | | 4 | **Oracles** | Active oracle feeds, price pair coverage, update frequency, network uptime, parachain integration status | Acurast, DIA Protocol, Chainlink (EVM parachains) | | 5 | **Bridges** | TVL, transfer volume, supported routes, fees, transfer times, trust model comparison (trustless vs. multisig) | Snowbridge, Hyperbridge, XCM (native), Wormhole | | 6 | **On-ramps / Off-ramps** | Supported fiat currencies, payment methods, geographic coverage, parachain token direct purchase support | Banxa, MoonPay, Transak, Ramp Network, Pendulum | | 7 | **Relayers** | XCM channel utilization, HRMP route health, message success rates, Snowbridge/Hyperbridge relayer performance | XCM Validators, Snowbridge Relayers, Hyperbridge Relayers, ParaSpell SDK | | 8 | **Explorers** | Network coverage, feature comparison (contract verification, XCM tracking, governance UI), data freshness | Subscan, Statescan, XCScan, Blockscout (EVM parachains) | | 9 | **Indexers** | Supported networks, query performance, Substrate vs EVM coverage, decentralization status | SubQuery, Subsquid (SQD), The Graph (EVM only) | | 10 | **Data Lakes** | Available datasets, query interfaces, update frequency, parachain coverage, API availability | Dune Analytics (substrate-etl), DotLake API, Google BigQuery |

Each category page includes: - **Current status** — what's available now - **Coverage heatmap** — which parachains are covered by which tools - **Gap analysis** — where infrastructure is missing vs. Ethereum/Solana benchmarks - **Links & resources** — direct links to tools, docs, and repos

### Pillar 2: Aggregated Ecosystem Metrics

| Module | Metrics Tracked | |--------|----------------| | **Ecosystem Overview** | Combined TVL across all parachains, aggregated active addresses (deduplicated), total extrinsic counts, ecosystem comparison vs. Cosmos/Avalanche/Solana | | **XCM Intelligence** | Cross-chain message volumes, top routes, HRMP channel utilization, success rates | | **Bridge Dashboard** | Snowbridge + Hyperbridge TVL, transfer volumes, fees, and route coverage | | **Hub Smart Contracts** | New REVM/PolkaVM deployments, contract interactions, developer adoption curves | | **Staking & Governance** | Network staking overview, validator/nominator counts, treasury balance and spend rate, referendum activity | | **Parachain Scorecards** | Individual pages per chain with TVL, users, transactions, coretime usage, token metrics |

---

## Technical Approach

### Data Sources (No New Infrastructure Required)

DotPulse aggregates existing publicly funded data sources — we're building the **presentation layer**, not reinventing the data pipeline:

- **Dune Analytics** (Ref #366) — SQL-queryable data for 50+ parachains via substrate-etl - **DotLake API** (Parity Data Team) — recently announced REST API for relay chain + parachain metrics - **DefiLlama API** — TVL data for individual parachains (we aggregate) - **Subscan API** — XCM transfers, extrinsics, staking data - **Polkadot Hub RPC** — Direct smart contract deployment and interaction data - **GitHub APIs** — Development activity tracking for infrastructure projects - **Public documentation & registries** — For infrastructure category mapping

### Architecture

| Layer | Technology | Purpose | |-------|-----------|---------| | Data Ingestion | Cron workers + API connectors | Pull from Dune, DotLake, DefiLlama, Subscan on schedule | | Backend | Rust (Actix-web) or TypeScript (Node.js) | REST API with caching, normalization, aggregation | | Database | PostgreSQL + TimescaleDB | Time-series optimized storage for historical metrics | | Frontend | Next.js + React + Recharts/D3.js | SSR dashboard with interactive charts | | Hosting | Vercel + Railway/Fly.io | Low-cost, scalable (free tier covers initial traffic) | | License | MIT (fully open-source) | Community can fork, extend, self-host |

---

## Milestones, Timeline & Budget

### Summary

| Milestone | Description | Timeline | Budget | |-----------|-------------|----------|--------| | **M1 — Foundation** | Data pipeline, backend API, database schema, infrastructure category data models | Weeks 1–4 | 3,400 DOT | | **M2 — Dashboard** | Frontend UI, 10 infrastructure category pages, ecosystem metrics views, XCM module | Weeks 5–9 | 4,200 DOT | | **M3 — Launch** | Hub tracker, comparison tools, embeddable widgets, docs, community launch | Weeks 10–12 | 2,200 DOT | | | **TOTAL** | **12 Weeks** | **9,800 DOT** |

### Milestone 1 — Foundation (Weeks 1–4) | 3,400 DOT

| Task | Description | Hours | |------|-------------|-------| | Data Source Integration | Connect to DotLake, Dune, DefiLlama, Subscan, GitHub APIs; build normalized data models | 40 | | Infrastructure Category Models | Data structures and collection logic for all 10 infrastructure categories (wallet support matrices, oracle feed inventories, bridge metrics, etc.) | 48 | | Aggregation Engine | Cross-chain TVL aggregation, address deduplication, metric normalization | 32 | | Backend API | REST endpoints for aggregated ecosystem data, infrastructure maps, time-series queries | 32 | | Database + Caching | TimescaleDB schema, Redis caching layer, migration scripts | 16 |

**M1 Deliverables:** Working backend API (publicly accessible), GitHub repo with full source code, API docs, data pipeline processing 15+ parachains and all 10 infrastructure categories populated with initial data.

### Milestone 2 — Dashboard UI (Weeks 5–9) | 4,200 DOT

| Task | Description | Hours | |------|-------------|-------| | Ecosystem Overview Page | Aggregated TVL charts, active users, transaction volume, headline metrics with time filters | 40 | | Infrastructure Category Pages | 10 dedicated pages with coverage heatmaps, gap analysis, project listings, and status indicators | 56 | | XCM Intelligence View | Cross-chain volume, top routes visualization, HRMP utilization, bridge comparison | 40 | | Parachain Scorecards | Individual chain pages with TVL, users, extrinsics, coretime, token info | 32 | | Responsive Design & UX | Mobile-first responsive, dark/light mode, loading states | 24 |

**M2 Deliverables:** Live beta dashboard, 10 infrastructure category pages, ecosystem overview, 15+ parachain scorecards, XCM analytics. Public beta link shared on Polkadot Forum for community feedback.

### Milestone 3 — Launch & Polish (Weeks 10–12) | 2,200 DOT

| Task | Description | Hours | |------|-------------|-------| | Hub Smart Contract Tracker | REVM/PolkaVM deployment counts, interaction volumes, developer metrics | 28 | | Ecosystem Comparison Module | Polkadot (aggregated) vs. Ethereum L2s, Cosmos, Avalanche side-by-side | 20 | | Embeddable Widgets | Chart widgets that ecosystem projects can embed on their own sites | 16 | | Docs & Deployment Guide | Contributor guide, self-hosting instructions, API reference, production deploy | 16 | | Community Launch | Forum post, X/Twitter announcement, feedback integration, v1.0 release | 8 |

**M3 Deliverables:** Production v1.0, Hub tracker, ecosystem comparison tool, embeddable widgets, comprehensive documentation, community launch.

### Budget Breakdown

| Category | Hours | Rate (USD/hr) | USD | DOT Equiv. | |----------|-------|---------------|-----|------------| | Full-Stack Development | 376 | $30 | $11,280 | 7,520 | | UI/UX Design | 40 | $25 | $1,000 | 667 | | DevOps & Infrastructure | 24 | $30 | $720 | 480 | | Documentation & Community | 16 | $25 | $400 | 267 | | Infrastructure Costs (12 months hosting) | — | — | $600 | 400 | | Contingency (5%) | — | — | $700 | 466 | | **TOTAL** | **456** | | **$14,700** | **9,800** |

*DOT conversion at ~$1.50/DOT. Will adjust at on-chain submission to match spot price.*

---

## Why These 10 Categories Matter

After conducting an in-depth infrastructure gap analysis of the Polkadot ecosystem across all 10 categories (benchmarked against Ethereum and Solana), here are the key findings that DotPulse will make visible:

**Strengths the ecosystem doesn't get credit for:** - **Bridges** are world-class — Snowbridge V2 (trustless, <$1 fees, ~$100M TVL) and Hyperbridge ($300M+ volume, ZK-verified) are best-in-class cross-chain infrastructure - **Wallets** are competitive — Nova Wallet (80K MAU, 410+ XCM routes), Talisman, SubWallet collectively cover 150+ networks - **Relayers** are architecturally superior — XCM messaging is native (no separate relayer network needed), with ParaSpell SDK providing unified call construction - **Data Lakes** are treasury-funded and mature — Dune (Ref #366), DotLake API, substrate-etl on BigQuery cover 50+ parachains

**Gaps that need attention (and that DotPulse will highlight to drive builder interest):** - **Oracles** are the most conspicuous deficit — no application-level VRF, no keeper/automation network, limited price feed coverage compared to Chainlink's 1000+ feeds on Ethereum - **Contract Standards** face a reset — ink! was discontinued (Refs 1760, 1773, 1796 rejected), Hub launched with dual VM but zero production-ready Solidity libraries with Polkadot-specific precompile wrappers - **Explorers** lack Hub support — Subscan covers ~100 networks but contract verification/interaction UI for Hub's REVM/PolkaVM contracts is missing - **On-ramps** are shallow for parachain tokens — Banxa/MoonPay support DOT purchases but buying parachain tokens directly still requires multi-step swaps

Making these gaps **visible and quantified** is the first step toward closing them. DotPulse creates the map that guides future treasury investment.

---

## Team: XXIX Labs (29Projects)

**Kunal — Founder & Lead Developer** - **Polkadot Fast Grants alumni** — delivered PowerGrid Network (decentralized virtual power plant with real IoT-blockchain integration using Substrate/FRAME) - Currently building Halo Protocol on Solana (50 beta users, 94% retention, zero defaults) - Multiple hackathon winner: UN COP'24 ISA Solarthon, Solana SuperteamDE - Multi-chain expertise: Polkadot, Solana, Ethereum, NEAR, Starknet (Rust, TypeScript, Solidity) - MS in Information Technology (in progress)

**Relevant experience:** Successfully delivered a Polkadot Fast Grant on time and within budget. Direct experience with Polkadot's data architecture, XCM messaging, Substrate runtime development, and parachain ecosystem. Full-stack development capability across the entire proposed tech stack.

---

## Success Metrics

| Metric | Target at Launch | Target at 3 Months Post-Launch | |--------|-----------------|-------------------------------| | Parachains tracked | 15+ active parachains | 25+ including Kusama | | Infrastructure categories populated | All 10 categories | All 10 with quarterly updates | | Data refresh rate | Every 30 minutes | Every 15 minutes | | API response time | < 500ms (p95) | < 300ms (p95) | | Monthly unique visitors | 500+ | 2,000+ | | API consumers | 5+ projects | 15+ projects | | Open source contributors | Codebase on GitHub | 3+ external contributors |

---

## Sustainability

**Phase 1 (Treasury-funded):** Build core platform, open-source all code, deploy production instance.

**Phase 2 (Community-sustained):** Accept community contributions via GitHub. Hosting costs are minimal (~$50/month) and can be covered by a Big Tipper proposal or absorbed by the team.

**Phase 3 (Revenue-optional):** Optional premium API tier for high-frequency data consumers while keeping the dashboard and standard API free permanently.

The MIT license ensures DotPulse survives regardless of the team's continued involvement. Anyone can fork, deploy, and extend.

---

## Risks & Mitigations

| Risk | Likelihood | Mitigation | |------|-----------|------------| | Data source API changes or rate limits | Medium | Multi-source redundancy; caching layer; fallback to SubQuery/Subsquid | | Scope creep beyond 12 weeks | Low | Fixed scope per milestone; additional features deferred to v1.1 | | Low initial adoption | Medium | Pre-launch community engagement; embeddable widgets drive organic adoption; infrastructure gap analysis creates immediate reference value | | DOT price volatility | Medium | Conservative pricing; contingency buffer; milestone-based payout | | Infrastructure data going stale | Medium | Automated data collection where possible; community contribution model for manual updates |

---

## Why Now

1. **Polkadot Hub launched smart contracts (January 2026)** — a new dimension of ecosystem activity that needs tracking from day one 2. **Data infrastructure is mature** — Dune (Ref #366), DotLake API, Subscan collectively cover 50+ parachains; the data layer is ready, the aggregation layer is missing 3. **Treasury is operating conservatively** — Q4 2025 saw $7.4M in spending (lowest since OpenGov). Small, high-leverage public goods align with fiscal discipline 4. **53% inflation cut incoming (March 2026)** — reduced treasury income makes it essential to maximize visibility per dollar 5. **JAM transition requires ecosystem-level metrics** — DotPulse architecture can adapt from tracking parachains to tracking JAM services in 2026–2027 6. **OpenZeppelin just added Hub support (February 2026)** — the smart contract ecosystem is about to accelerate and needs monitoring

---

## Accountability

- Milestone reports posted on Polkassembly/SubSquare at each completion with deliverable links - All code open-source on GitHub from day one (not just at final delivery) - Final report with KPI assessment, lessons learned, and future roadmap - Permanent PDF of proposal stored on Crust/IPFS - Available for community Q&A throughout decision period and development

---

## Contact

- **Organization:** XXIX Labs (29Projects) - **GitHub:** github.com/xxix-labs - **Contact:** hello@29projectslab.com - **Polkadot Address (Beneficiary):** 1U3JboaBjPViEFDwwzKpFLVeV2LHQx9Jy31FuMgHuRBnmxq

---

*Looking forward to community feedback on scope, budget, and priority categories. Happy to jump on OpenGov.Watch Office Hours or any community call to discuss.*

*DotPulse: Making Polkadot's infrastructure strength and ecosystem scale visible to the world.*