77 articles in this category
io.net is the fastest-moving GPU network in DePIN — and the easiest to misread. Here is how to query worker counts, device breakdowns, and the registered-vs-active utilization gap that most dashboards hide.
Livepeer is the video-transcoding DePIN. Its data picture is transcoders, orchestrators, and delegators around a staking layer. Here is how to query them through canonical, verifiable concepts.
How a Merkle root guarantees batch integrity for DePIN telemetry: hash the batch, root it, anchor it to Bitcoin. Here is the mechanism, and why it means you never have to trust the provider.
DePIN data provenance has three layers: a verify_url on every value, a Merkle root on every batch, and a Bitcoin timestamp on every root. Together they make any number cryptographically checkable.
The most complete DePIN networks list available: 800 projects catalogued, 327 with live data. Here is what the list contains, what the coverage tiers mean, and how to query it.
The backbone of DePIN on-chain data is direct RPC access. Here is how we read 9 blockchains from first-party RPC endpoints — Ethereum, BSC, Solana, Bittensor, and more — with no third-party indexer in the path.
A number with no source is an opinion. DePIN data provenance is the practice of giving every value a receipt — a source, an as-of timestamp, a verify_url, and a freshness verdict. Here is why it matters and how it works.
DePIN TVL measures value locked into networks — staked tokens, secured collateral, and reserves. Here is how we track TVL across infrastructure networks and why it reads differently than DeFi TVL.
Bittensor is the largest single source in our DePIN coverage. We decode 129 subnets directly from the Finney chain — neurons, validators, alpha pools, and TAO emission — with no third-party indexer in the path.
Node count is the most-quoted — and most-inflated — DePIN metric. Here is how we track verifiable active node counts across 372 networks, and why registered counts hide the real story.
Storj is a storage DePIN with a satellite architecture that makes its data picture subtle. Here is how to query storage nodes, satellites, and real capacity — and why the two-denominator problem matters.
One public URL, one second, four defensible node counts. Storj's us1 satellite reports 123,580 total nodes but only 32,796 active — a 3.8x gap that is entirely dead history. Which number is 'the node count' depends on which denominator you accept, and a third trap (summing satellites) overstates the fleet ~4x. Every number here is re-checkable from the same public endpoint.