DePIN supply data is the scarce layer of infrastructure intelligence. While anyone can pull token prices from CoinGecko, reading a network's own API or blockchain to get actual node counts, GPU supply, storage capacity, and staking data requires building and maintaining collectors per network.
We read directly from 69 distinct data sources including Solana RPC, Ethereum RPC, BSC RPC, Bittensor subtensor, EVM blockscout explorers, and per-network stats APIs (Akash, Helium, Storj, Filecoin, io.net, and more).
| Metric | Example | Source |
|---|---|---|
| Active nodes | Helium 375K hotspots | helium_entity_api |
| GPU supply | io.net 2,020 GPUs | io_explorer |
| Storage capacity | Filecoin 1.2K PiB | filfox |
| Token supply | AKT 383M circulating | ethereum_rpc |
| Validator count | Cosmos 180 validators | cosmos_lcd |
Supply figures are read from CoinGecko and each network's own chain, and the two are distinguished: market aggregators and first-party reads are labeled separately on every value. Where a network publishes circulating and total supply, both are captured with their own as_of timestamps; where published dashboards disagree with on-chain reads, both readings are kept — revisions are recorded, not overwritten.
Independent confirmation of reported supply is part of the weekly brief: how much of each token's reported supply can be confirmed on-chain, and where exchange balances moved. The same verify_url discipline applies — every supply value links to the exact source that produced it, and the Bitcoin-anchored daily batch proves the dataset wasn't changed after the fact.