A short guide for general readers
When a digital asset is described as “in demand,” that phrase can mean many different things — and the differences matter more than they might initially appear.
An asset can be in demand because millions of people pass through it briefly every day. It can also be in demand because a smaller number of institutions must hold it continuously — as collateral, as a liquidity buffer, as a reserve against operational failure, or because removing it would break something that depends on it.
These are not the same kind of demand. The first is transaction volume. The second is something closer to structural necessity.
Conflating the two is one of the most common errors in analyzing digital assets — and it produces conclusions that look rigorous but rest on a category mistake.
The Retained-Demand Audit Series is built around this distinction. Its core question is simple: Does someone need to hold this asset, or do they only need to use it briefly on the way to something else?
Usage is not the same as retained demand.
When an asset is used in a transaction — even a very large one — it may only need to be held for a fraction of a second. A bridge asset, a settlement token, a conversion intermediate: high volume, near-zero holding time. The asset moves through, and no one carries it on a balance sheet.
Retained demand is different. It refers to the demand that arises specifically from the need to hold an asset: to keep it available, to maintain it as a reserve, to rely on it as a buffer or a backstop. The holding is not incidental to the use — the holding is the use.
This distinction shapes what kinds of questions an audit should ask:
The answers to those questions are not the same as knowing how much the asset transacts.
The failure mode is not malicious. It usually comes from applying a familiar metric — transaction volume, adoption announcements, integration partnerships — to a question that metric was not designed to answer.
Some patterns worth recognizing:
Adoption does not equal necessity. An asset can be integrated into a system without being load-bearing. Integration tells you it is present. It does not tell you what happens if it is removed.
Transaction volume does not equal holding time. High throughput may indicate that an asset is efficient precisely because it does not need to be held. Speed and brevity of holding can be a feature of the design, not evidence of retained demand.
Customer utility does not equal asset necessity. An end user may find a service useful without any need to hold the underlying asset. The utility flows through the asset; it does not require accumulation of it.
Endorsement does not equal structural dependence. Institutional participation in a network — announcements, pilots, stated interest — does not by itself indicate that the institution’s balance sheet depends on the asset.
Each of these substitutions produces a picture of demand that may look compelling but is measuring the wrong thing.
Consider a shipping route. Cargo moves through a port city every day — enormous volumes, continuously. The port is clearly in use. But which businesses in that city are dependent on the port? Which ones have built their inventory systems, their contracts, their financial reserves around continuous access to it?
The answer to that second question is not the same as counting cargo volume. Most of what passes through a port is in transit. The retained demand — the demand that survives when you ask “what breaks if this stops?” — is a different and smaller number.
The same logic applies to digital assets. High transaction volume through a settlement layer tells you something real. It does not tell you whether any counterparty has a structural reason to hold the asset rather than simply route through it.
Retained demand asks the second question. Most analyses stop at the first.
The Retained-Demand Audit Series does not produce investment recommendations, price forecasts, or verdicts on specific assets. It is a research archive built around methodology.
Its focus is on making the distinction between usage and retained demand auditable — that is, visible, documented, and open to challenge and revision.
This involves frameworks for:
The audit framing is deliberate. The goal is not to produce a single confident answer, but to make the reasoning behind any answer legible — so that it can be scrutinized, corrected, and updated as conditions change.
This series is not a case for any particular digital asset. The methodology is designed to be applied across contexts, and any asset that appears in the analysis is there as a subject of examination, not advocacy.
It is not investment advice. The research operates at the level of analytical frameworks, not at the level of portfolio recommendations.
It is not a claim that retained demand is high or growing for any specific asset. That would be a conclusion reached by applying the methodology — not a premise of it.
It is not a completed system. The series is an active archive. Positions within it are explicitly provisional, and revision conditions are part of the research design.
The full research archive is available here:
The archive includes working papers, summaries, Phase II materials, and the README, which develop the core methodology in greater depth.
If you are approaching from the AI-collaboration and epistemic-structure side, see also:
This page is a general reader’s entry point. It is not a substitute for the primary research documents, and it does not represent the full scope or methodology of the series.