Our DePIN dataset is built to be irresistible because it is checkable. Every value names the source it was read from and links straight to it. Every daily batch is Merkle-rooted and timestamped to Bitcoin. You do not have to trust us — you can verify.
Counts measured live from our datalake on 2026-08-09 and growing. Numbers on this page are what we can show and defend, never rounded up past what we measured.
The atom of our dataset is not a number — it is a number with its paperwork. Every value we serve carries the same seven-field shape.
{
"symbol": "AKT",
"metric": "price_usd",
"value": 0.506855,
"unit": "usd",
"source": "CoinGecko /coins/markets",
"verify_url": "https://www.coingecko.com/en/coins/akash-network",
"as_of": "2026-08-09T17:15:20Z"
}symbol / metric — what this measures, keyed so agents can join it.
value / unit — the measured number and its unit. Never rounded up past source.
source — the exact upstream feed the value was read from.
verify_url — a link you can open right now to check the value at that source.
as_of — the timestamp the value was true. Stale is shown, never hidden.This is a real row from today's batch. The verify_url resolves to the source page for Akash's market data — open it and compare.
We do not pretend everything is first-party. Each series is labelled with the tier it came from. The largest tier is read directly from the network's own API or chain; the rest are named market and protocol aggregators.
| Source tier | Live series | What it is |
|---|---|---|
| depin_first_party | 595 | Read straight from the network's own API / chain — verify_url points to the network itself. |
| coingecko | 58 | Market facts: price, market cap, circulating & total supply. |
| defillama | 51 | Protocol TVL plus fees and revenue. |
| github | 14 | Developer-activity telemetry. |
| akash_console | 13 | Akash provider / lease telemetry. |
| weatherxm_api | 10 | WeatherXM station telemetry. |
| flux_api | 7 | Flux node telemetry. |
Every value keeps its tier label all the way to your query, so an integration always knows whether a number came from the network itself or from an aggregator.
Most data vendors ask you to trust a dashboard. We do the opposite: each value hands you the upstream link it was read from, so you can confirm it without us in the loop.
verify_url proves a value is real at its source. The Bitcoin anchor proves we did not quietly change it afterwards. Once a day we take the whole batch, build a Merkle tree, and timestamp its root to Bitcoin through OpenTimestamps — free, no token, no spend.
symbol · metric · value · unit · source · verify_url · as_of
Each row is hashed into a Merkle leaf.
All leaves fold into one 32-byte root for the day.
The root is committed to four independent OpenTimestamps calendars.
The calendars' commitment settles into a Bitcoin block.
leaf = sha256( "symbol\tmetric\tvalue\tunit\tsource\tverify_url\tas_of" )
root = merkle( sort(all rows) ) // odd node duplicates last
stamp = ots stamp root // submitted to 4 public calendars1. pull the batch you were served.
2. sha256 each row, Merkle-root them.
3. confirm it equals the published root.
4. ots verify batch.root.ots // checks the root against BitcoinIt proves integrity and point-in-time: that this exact set of 1,369 values existed on 2026-08-09 and has not been altered since. Recompute the root, run ots verify, and the timestamp settles against the Bitcoin blockchain — no trust in Kairos required.
It does not prove that a source value is correct — that is what the per-value verify_url is for, upstream — and it says nothing about trading performance, returns, or signal accuracy. This is a data-integrity guarantee on a data product, not a track-record claim.
Today's root is submitted to four calendars and is pending Bitcoin confirmation. Calendars batch submissions and commit to a Bitcoin transaction on their cycle; once that transaction is mined, ots upgrade completes the proof and ots verify checks it against the chain. A public per-value inclusion-proof endpoint ships with the API.
When a network has no free or first-party feed, we do not invent a number to fill the gap. We keep the network in the catalog and mark the gap, so you always know the difference between "we measured this" and "no public feed exists".
The catalog spans 385 network entries across compute, storage, sensor, wireless, AI, energy and mobility — the map of the territory, not just the covered part.
Each catalog entry records whether a public stats API exists and its URL. As of today 30 entries carry a public stats-API URL; the rest are cataloged with the gap shown, not hidden.
Provenance-or-silence. If we cannot read a value from a real source, the field stays empty and labelled — never back-filled with a guess.
The dataset is delivered through a structured API with the same provenance shape on every field — designed for AI agents, MCP clients, and analysts who need to cite their sources.
See the coverage and depth, or read how we verify a single number end to end.