Crypto incentives meet real-world infrastructure demand

Track the DePIN networks turning hardware into open infrastructure markets.

A practical research hub for compute, GPU, storage, wireless, mapping, and data networks. Compare demand signals, node economics, token risk, and operator fit before you spend time or budget on deeper diligence.

Explore projects Check node economics

Research angle

Follow infrastructure that has users, not just emissions.

01

Demand before rewards

Prioritize networks with visible customers, recurring usage, and credible revenue.

02

Operator realism

Compare hardware cost, uptime burden, geography, bandwidth, and maintenance needs.

03

Token durability

Separate sustainable marketplace fees from short-lived token incentive programs.

Sector lens

Compare categories by demand proof and operator friction.

Each sector has a different diligence pattern. Use these prompts to decide which assumptions need evidence before spending time, capital, or hardware.

Methodology

How to read this DePIN watchlist.

Primary-source first

Project cards link to official sites and docs so readers can verify operator requirements, network rules, and current claims before relying on summaries.

Scenario, not advice

Calculator output is a rough screen for deeper diligence. It does not account for taxes, token liquidity, downtime, replacement hardware, or local regulations.

Evidence over emissions

Reviews emphasize demand signals, customer usage, and operator constraints rather than headline reward rates or short-term incentive campaigns.

Data freshness

Treat review dates as content freshness markers. Re-check source links, rewards, fees, and hardware assumptions before publishing dated claims.

Source quality

Each card now separates sources from claims to refresh.

Directory metadata uses official project sources first, records when sources were last checked, and lists the evidence gaps that need a dated source before publication.

Dated source checks

Every project card carries a source checked date from the shared research snapshot. Treat it as a freshness marker, not proof that live rewards or rules are unchanged.

Evidence gaps

Cards flag the metrics that need refreshed verification, such as utilization, local coverage, data buyers, or operator requirements.

Publication standard

Public examples should cite dated primary sources and repeat the calculator exclusions whenever scenario output appears near operator assumptions.

Reviewer checklist

Turn evidence snapshots into publication decisions.

Use this local workflow before expanding a profile, adding calculator examples, or writing dated claims. It relies on the stored evidence snapshot templates and does not fetch live URLs.

Reviewer checklist export page

Collect dated evidence notes before publishing claims.

This local-only export page combines reviewer checklist items, dated evidence note templates, manual QA evidence logs, and publication blockers. It is for review records only and does not fetch live URLs, store private reviewer notes, or support income forecasts.

Download static markdown template

Use the static markdown file for local notes only. Keep screenshots, account identifiers, reviewer contact details, and raw private source notes outside the public site.

Final readiness dashboard

Roll up profile coverage, freshness, and QA evidence locally.

This dashboard summarizes source freshness counts, profile evidence inventory, static link checks, and publication blockers before any current metrics or calculator examples are expanded. It also points reviewers to the saved final report artifact and manual handoff checklist without fetching live URLs or treating scaffold dates as current source proof.

Profile QA status dashboard

Track profile readiness before expanding dated claims.

This local dashboard summarizes source freshness decisions, profile coverage, and blockers without treating a scaffold date as proof that rewards, usage, rules, or privacy terms are current.

Stale-claim and privacy wording checks

Block current claims until dated evidence exists.

Use this copy review before publishing data-network, contributor, policy, or calculator wording. It keeps privacy-sensitive notes out of the static site and avoids income or investment framing.

Project directory

Compare DePIN sectors by user demand and operator complexity.

Filter the launch list by sector. Each project card includes a practical operator lens and a fast view of revenue maturity.

10 project reviews

Short-form diligence for the current DePIN watchlist.

Reviews focus on what matters before allocating time or hardware: demand proof, operator fit, and the biggest risk to monitor.

DePIN guides · 12 articles

SEO research library for operators and investors.

Beginner explainers, setup guides, GPU comparisons, tokenomics, regulation, and outlook pieces. Start with What Is DePIN? or browse by topic below.

What Is DePIN?

Foundation explainer for decentralized physical infrastructure networks.

DePIN and AI

How decentralized compute fits machine-learning workloads.

Related sites: RWA Tokenization Hub · AI Crypto Agents · Stablecoin Payments

Local profile index

Filter dated scaffolds by sector and review priority.

Each profile repeats the review date, not-advice framing, source checklist, operator assumptions, demand questions, and evidence snapshot template before any future expansion.

Node profitability checklist

Estimate whether a deployment deserves a deeper model.

This checklist is not financial advice. It is a pre-flight screen for hardware, bandwidth, incentive, and operational assumptions.

Inputs are bounded placeholders for a scenario screen. Replace them with dated source checks for rewards, fees, power, hardware quotes, and liquidity before publishing.

This is a screening tool, not investment advice or an income forecast. Verify live rewards, token liquidity, local costs, taxes, and hardware resale assumptions before making decisions.

Before modeling hardware

  • Confirm the network has real paying users or a credible path to them.
  • Model rewards after token unlocks, validator dilution, and marketplace fees.
  • Check if your location improves earnings through coverage, latency, or supply gaps.
  • Price electricity, bandwidth, storage, maintenance time, and replacement parts.
  • Understand slashing, uptime penalties, KYC, warranties, and protocol governance.
  • Define a review trigger for when assumptions miss the modeled scenario for three consecutive months.

Calculator assumptions

    Publication caveat docs

    Treat every result as a scenario screen. Before publication, record dated source checks for rewards or fees, token price and liquidity haircut, hardware quote and resale value, electricity, bandwidth, storage, maintenance, taxes, downtime, depreciation, local legal obligations, and compliance costs.

    Scenario examples with caveats

    Calculator example review log

    Browser and static QA

    Manual checks before publishing profile updates.

    Run these checks locally after content edits. They complement the Node check script and avoid live source fetching, account access, or external services.

    Browser pass

    • Open the homepage and one profile at desktop and narrow mobile widths.
    • Tab through skip links, filter buttons, profile anchors, source buttons, and calculator fields.
    • Confirm profile snapshot tables scroll horizontally without hiding source or dated-field columns.

    Static pass

    • Verify one h1, meta description, local anchors, profile index link, and reviews link per profile.
    • Confirm source freshness decision statuses match evidence gaps and do not imply current metrics.
    • Run npm run check before linking new dated analysis from review cards.

    Calculator pass

    • Try zero, high, and haircut-heavy inputs to confirm bounded scenario output.
    • Keep not-advice and not-income-forecast copy visible near result examples.
    • Document excluded costs before using any scenario in a profile or market note.

    Weekly infrastructure market note

    This week: AI demand keeps GPU networks relevant, but buyers still want reliability.

    Decentralized GPU and compute networks remain the highest-attention DePIN segment because AI teams want lower-cost capacity and flexible supply. The strongest projects are moving from token-subsidized supply growth toward measurable customer usage, better scheduling, and enterprise-grade service guarantees.

    Storage and data networks are less speculative when demand is anchored to durable use cases like archival storage, indexing, weather data, or mobility intelligence. Wireless and mapping continue to depend heavily on geographic density: operators should avoid chasing headline APY without confirming local coverage gaps.

    Signal to watch: marketplace revenue as a share of total rewards. Review the directory

    Stay updated

    Get DePIN research updates and new profiles.

    Infrequent updates on new reviews, sector analysis, and research tools. No spam, no token shilling, no investment advice.

    Business model

    Built for content, affiliate, sponsorship, and consulting paths.

    Affiliate guides

    Hardware, node hosting, monitoring, VPN, cloud GPU, and storage provider comparisons.

    Paid calculators

    Operator-grade models for token emissions, power cost, depreciation, and scenario planning.

    Sponsorships

    Network launches, infrastructure tooling, dashboards, and analytics providers.

    Consulting

    Node operations playbooks, content strategy, and market research for DePIN teams.