DePIN due diligence grounded in observable evidence

Investigate a defined network or research question using the evidence that is actually available. Start with the networks, measurements, time period, and intended deliverable. We establish what can be observed, where comparisons are valid, and which questions remain unanswered. Deliverables, collection periods, delivery formats, and source-specific usage conditions are agreed before work begins — where a requested measurement is unavailable or unsuitable, the limitation is part of the findings, not a gap filled with an unsupported estimate.

Capacity is not the same as utilisation, and utilisation is not proof of paying demand. A ratio is meaningful only when its numerator, denominator, units and observation time are compatible. A cross-network comparison also needs comparable definitions; a shared label is not enough.

The former table contained an August 2026 example, not current measurements. For selected available observations, inspect the public preview and its per-row source and timestamp. A live source URL can verify the current response; it does not by itself reproduce a historical value.

Inspect the evidence before commissioning work

The preview shows selected available observations, with missing and unresolved verification links identified. It is not a complete network inventory or a certification of every value.

Inspect the public data preview

Inspect an upstream source

# Current Akash Console response, not an archived replay or a commercial-use licence.
curl -fsS https://console-api.akash.network/v1/network-capacity | jq '.resources.gpu'

Check the returned definitions, units and timestamp before calculating a ratio. Availability does not establish redistribution rights.

The engagement

Scope

You name the networks. We establish whether utilisation is observable at all — that answer alone may be unavailable; that limitation is a finding, not an estimate.
Where it is observable and the intended use is permitted, we agree a collection period and cadence, then report compatible ratios and changes, with their definitions and limitations.
Delivered observations include source, timestamp and measurement method. Historical replay is included only where the retained inputs and source terms support it.
Where it is not observable, we say so in writing and explain what would have to change. We do not fill the gap with a model.

What you get

A written findings memo per network, with provenance for every number.
Daily machine-readable feed for the engagement period, via API or file.
Documented collection methods; code delivery and licensing only where agreed and permitted.

Price and permitted scope

Price and deliverables are agreed in writing before work starts. Source-specific usage rights are reviewed before any commercial redistribution; unavailable permissions narrow the scope.

What this is not

Not price prediction. Not a token rating. Not a model output dressed as a measurement.
Not a subscription — it is scoped work with a named deliverable.

Honest limits, stated up front. Coverage and historical depth vary by network and source. A fresh timestamp, a working URL or an on-chain origin is not by itself proof of measurement validity, complete historical replay or commercial-use permission. The engagement names its supported inputs and unresolved questions. No missing metric is estimated or zero-filled.

Talk to us

Engagements are scoped per network set. If you are doing diligence on a DePIN position and want to know whether the demand side is real, start here.

Start a diligence engagement Or buy the data directly

Prefer to evaluate first? Every product has its own access and usage conditions. Start with the public preview, which does not require payment.