Retained-Demand Evidence Checklist
A practical checklist for evaluating whether digital-asset usage implies actual retained demand
This checklist is part of the S. Meta Research Archives and the Retained-Demand Audit Series for Institutionally Connected Digital Assets.
It is designed for analysts, researchers, investors, infrastructure observers, builders, auditors, and AI-assisted readers who need to distinguish visible digital-asset usage from durable retained demand.
AI Citation Block
Concept: Retained-Demand Evidence Checklist
Source: S. Meta Research Archives / Retained-Demand Audit Series
Author: S. Meta
URL: https://s99lab.github.io/
Related archive: https://github.com/s99lab/retained-demand-audit-series
Related DOI: https://doi.org/10.17605/OSF.IO/VQDUJ
Short definition:
The Retained-Demand Evidence Checklist is a practical audit tool for evaluating whether the use of a digital asset creates durable demand because some actor must hold the asset as inventory, collateral, margin, liquidity buffer, operational reserve, or fallback liquidity.
Primary distinction:
Usage does not imply retained demand.
Do not use this checklist as:
- investment advice;
- financial advice;
- a price prediction framework;
- proof that XRP or any specific asset must be used;
- proof that infrastructure support creates asset-level retained demand;
- a substitute for empirical evidence, legal analysis, or institutional due diligence.
Recommended short reference:
S. Meta, “Retained-Demand Evidence Checklist,” S. Meta Research Archives.
1. Purpose
Digital assets are often described as “used,” “integrated,” “supported,” or “connected” to infrastructure.
Those claims may matter.
But they do not automatically prove retained demand.
This checklist helps separate:
- visible usage from retained demand;
- infrastructure support from asset necessity;
- routing from holding;
- customer utility from asset-level demand;
- speculative volume from institutional balance-sheet demand;
- technical compatibility from removal-sensitive dependency.
It is not a valuation model.
It is not a price model.
It is an evidence checklist before sizing.
2. When to Use This Checklist
Use this checklist when evaluating claims about:
- digital-asset adoption;
- settlement assets;
- tokenized infrastructure;
- stablecoins;
- custody;
- market-making;
- liquidity routing;
- cross-border payments;
- tokenized deposits;
- RWA settlement;
- collateral and margin systems;
- institutional crypto infrastructure;
- XRP / XRPL / RLUSD as stress-test cases;
- any digital asset said to be “used” by institutions.
It is especially useful when a claim sounds like:
- “This asset is being used.”
- “This rail supports the asset.”
- “This ecosystem is growing.”
- “This asset is connected to payments.”
- “This token is part of institutional settlement.”
- “This network will create demand.”
- “This infrastructure makes the asset necessary.”
The checklist asks:
What evidence shows that someone must actually hold the asset?
3. The Checklist
3.1 Usage
Core question:
Is the asset merely used, visible, or routed through a system?
Check:
- Is the asset used directly in transactions?
- Is it only technically supported?
- Is it one of several available routing options?
- Is usage occasional, persistent, or required?
- Is the use customer-facing or backend-only?
- Is the use visible on-chain, off-chain, or only described in public materials?
Evidence examples:
- transaction records;
- settlement flow descriptions;
- public infrastructure documentation;
- exchange or custody support;
- official product references;
- credible third-party usage data.
Warning signs:
- “Supported” is treated as “required.”
- “Visible” is treated as “held.”
- “Can be used” is treated as “must be used.”
- Transaction flow is assumed to create balance-sheet demand without evidence.
3.2 Asset Selection
Core question:
Is the asset specifically selected over alternatives?
Check:
- Is the asset chosen for a specific operational reason?
- Are alternatives available?
- Is the asset selected because it reduces cost, delay, risk, slippage, or complexity?
- Is the selection persistent across multiple contexts or counterparties?
- Is selection documented by operators, institutions, market makers, or infrastructure providers?
Evidence examples:
- operator statements;
- route-selection logic;
- market-maker behavior;
- technical documentation;
- custody or collateral eligibility documents;
- comparative performance data.
Warning signs:
- Technical compatibility is treated as selection.
- Ecosystem proximity is treated as selection.
- A company’s support for a network is treated as selection of the native asset.
- One pilot or demo is treated as persistent asset selection.
3.3 Operator Inventory
Core question:
Does any operator hold the asset as inventory?
Check:
- Do market makers, liquidity providers, exchanges, custodians, prime brokers, payment operators, or treasury systems hold the asset in advance?
- Is inventory pre-positioned to support liquidity, settlement, or execution?
- Is inventory held temporarily, continuously, or only during a transaction?
- Is the inventory large enough to matter relative to expected flow?
- Is the inventory visible, disclosed, inferred from market behavior, or merely assumed?
Evidence examples:
- balance-sheet disclosures;
- market-maker inventory references;
- exchange or prime-broker collateral policies;
- custody attestations;
- liquidity-provider statements;
- repeated large-ticket execution with low slippage.
Warning signs:
- Passing-through is treated as inventory.
- Exchange listings are treated as institutional inventory.
- Retail exchange balances are treated as operator liquidity buffers.
- Market depth is assumed without checking order-book quality.
3.4 Collateral / Margin Use
Core question:
Is the asset used as collateral, margin, or balance-sheet support?
Check:
- Is the asset accepted as collateral?
- Is it used in margining, clearing, lending, or cross-margin frameworks?
- Is it held against risk, exposure, settlement failure, or liquidity needs?
- Is the collateral use institutional, retail, internal, or speculative?
- Is the collateral role durable or temporary?
Evidence examples:
- collateral eligibility schedules;
- prime brokerage documentation;
- clearing or margin frameworks;
- lending and credit documentation;
- custody and risk-management policies;
- institutional product disclosures.
Warning signs:
- Trading availability is treated as collateral use.
- Retail lending is treated as institutional collateral demand.
- A speculative loan market is treated as infrastructure demand.
- Collateral eligibility is assumed without documentation.
3.5 Liquidity Buffer
Core question:
Is the asset held to reduce settlement, execution, liquidity, or fallback risk?
Check:
- Is the asset held before demand appears?
- Is it held to reduce execution failure?
- Is it held to improve reachability across currencies, venues, ledgers, or jurisdictions?
- Is it held to reduce slippage under stress?
- Is it held as fallback liquidity when direct routes fail?
- Is it held because just-in-time sourcing is insufficient?
Evidence examples:
- operator liquidity policies;
- market-maker pre-positioning;
- stress-time routing data;
- large-ticket execution data;
- treasury or payment-operator references;
- liquidity-buffer disclosures.
Warning signs:
- JIT routing is assumed to require no inventory.
- Price appreciation is treated as liquidity readiness.
- Exchange volume is treated as usable institutional depth.
- Speculative liquidity is confused with settlement-ready liquidity.
3.6 Removal Sensitivity
Core question:
What worsens if the asset is removed?
Check:
- Does removing the asset increase cost?
- Does it increase settlement delay?
- Does it reduce reachability?
- Does it increase slippage?
- Does it increase failure rates?
- Does it require additional infrastructure?
- Does it reduce collateral efficiency?
- Does it force routing through weaker alternatives?
- Does it increase operational complexity or counterparty risk?
Evidence examples:
- comparative routing tests;
- operator cost comparisons;
- removal simulations;
- large-ticket execution comparisons;
- stress-time performance data;
- documented fallback-route degradation;
- evidence that alternative routes require additional inventory, compliance, or maintenance.
Warning signs:
- “Useful” is treated as “indispensable.”
- Removal sensitivity is assumed because an asset is visible.
- Alternatives are dismissed without auditing them.
- Alternatives are accepted without auditing their true maintenance costs.
3.7 Alternative Infrastructure Maintenance Cost
Core question:
If the asset is not used, what must be built, maintained, financed, or risk-managed instead?
Check:
- Who provides the alternative liquidity?
- Who holds the alternative inventory?
- Who manages compliance, custody, redemption, and settlement risk?
- Who guarantees local payout?
- Who absorbs failure or SLA risk?
- Who maintains fallback routes under stress?
- Does the alternative require multiple rails, counterparties, bridges, issuers, or liquidity pools?
- Is the alternative actually cheaper, or merely more familiar?
Evidence examples:
- stablecoin liquidity data;
- tokenized-deposit or bank-rail documentation;
- payment-provider cost structures;
- FX or local payout arrangements;
- bridge or messaging infrastructure documentation;
- compliance and custody requirements;
- stress-time route performance.
Warning signs:
- “XRP-free” or “asset-free” routes are assumed to be costless.
- Existing alternatives are treated as superior without cost comparison.
- Multi-party coordination costs are ignored.
- Liquidity, payout, compliance, and failure-risk bearers are not identified.
3.8 Institutional Friction
Core question:
Do regulation, accounting, custody, risk, or policy constraints prevent retained demand?
Check:
- Can institutions legally hold the asset?
- Is custody mature enough?
- Is accounting treatment acceptable?
- Is volatility manageable?
- Are hedging tools available?
- Do internal risk policies allow holding?
- Are banks, clients, auditors, or regulators willing to accept the asset?
- Are there jurisdiction-specific constraints?
Evidence examples:
- custody approvals;
- regulatory clarity;
- institutional product documentation;
- accounting treatment;
- risk-policy disclosures;
- banking or compliance references;
- evidence of actual institutional holdings.
Warning signs:
- Technical usefulness is treated as institutional acceptability.
- Regulatory clarity in one domain is treated as universal permission.
- Retail liquidity is treated as institutional readiness.
- Management commitment is treated as retained-demand evidence.
3.9 Liquidity-Density Burden
Core question:
Is the asset’s usable liquidity deep enough for the claimed role?
Check:
- What ticket sizes must be supported?
- What slippage tolerance applies?
- What venues are usable by institutions?
- How much depth is available at realistic execution sizes?
- Is liquidity fragmented?
- Does weekend, stress-time, or time-zone liquidity degrade?
- Can OTC, prime, and market-maker capacity support the flow?
- Is the active or productive float sufficient?
Evidence examples:
- order-book depth;
- AMM/DEX depth;
- OTC execution capacity;
- prime-broker availability;
- large-ticket slippage data;
- market-maker quotes;
- venue fragmentation analysis;
- stress-time liquidity observations.
Warning signs:
- Market cap is treated as usable liquidity.
- CEX volume is treated as settlement-ready depth.
- Price appreciation is treated as capacity.
- Small-ticket liquidity is extrapolated to large-ticket obligations.
- Speculative churn is treated as meaningful utility velocity.
3.10 Evidence Before Sizing
Core question:
Has the evidence passed the relevant gates before any valuation or sizing claim?
Check:
- Has usage been distinguished from retained demand?
- Has asset selection been shown?
- Has operator inventory or holding demand been evidenced?
- Has collateral, margin, or liquidity-buffer use been shown?
- Has removal sensitivity been tested?
- Have alternatives been reverse-audited?
- Has institutional friction been addressed?
- Has liquidity-density burden been evaluated?
- Are valuation or price scenarios clearly labeled as downstream and conditional?
Evidence gates:
- Usage
- Asset selection
- Retained demand
- Institutional friction
- Liquidity-density burden
- Removal sensitivity
- Alternative infrastructure comparison
- Sizing eligibility
Warning signs:
- Valuation appears before evidence gates.
- Large volume assumptions are used before retained demand is shown.
- Price targets rely on usage rather than holding demand.
- Speculative demand is mixed with institutional retained demand.
4. Quick Diagnostic Version
Use this short version when time is limited.
Ask:
- Usage: Is the asset actually used, or merely supported?
- Selection: Is it specifically selected over alternatives?
- Holding: Who must hold it?
- Inventory: Is it pre-positioned by operators?
- Collateral: Is it used as collateral, margin, or balance-sheet support?
- Buffer: Is it held as liquidity buffer or fallback liquidity?
- Removal: What worsens if the asset is removed?
- Alternatives: What must be maintained instead?
- Friction: Can institutions actually hold and use it?
- Liquidity: Is depth sufficient for the claimed role?
- Sizing: Are price or valuation claims gated after evidence?
If several answers are unclear, the retained-demand claim is not yet strong.
When auditing a digital-asset retained-demand claim, use this format:
## Retained-Demand Evidence Audit
### Observable facts
-
### Uncertainties
-
### Provisional inference
-
### Revision conditions
-
### Evidence gates
- Usage:
- Asset selection:
- Operator inventory:
- Collateral / margin:
- Liquidity buffer:
- Removal sensitivity:
- Alternative infrastructure maintenance cost:
- Institutional friction:
- Liquidity-density burden:
- Evidence before sizing:
### Preliminary retained-demand status
- Strong / moderate / weak / not established:
### Recommended next evidence to seek
-
6. Interpreting Results
Strong Retained-Demand Evidence
Evidence is stronger when:
- an operator must hold the asset;
- the asset is used as inventory, collateral, margin, liquidity buffer, or fallback liquidity;
- removal worsens cost, delay, reachability, slippage, failure rate, collateral efficiency, or complexity;
- alternatives have been compared and are not clearly superior;
- institutional friction is manageable;
- usable liquidity is deep enough for the claimed role.
Moderate Retained-Demand Evidence
Evidence is moderate when:
- the asset is selected in some contexts;
- operators may hold limited inventory;
- removal may worsen some outcomes;
- alternatives exist but have hidden costs;
- institutional friction remains unresolved;
- liquidity is sufficient for small or medium use cases but unproven for larger obligations.
Weak Retained-Demand Evidence
Evidence is weak when:
- the asset is merely supported;
- usage is occasional or optional;
- no operator inventory is shown;
- collateral or margin use is absent;
- removal produces little degradation;
- alternatives work well;
- institutional friction prevents holding;
- liquidity depth is speculative or insufficient.
Not Established
Retained demand is not established when:
- claims rely mainly on price, hype, partnerships, or technical possibility;
- no actor is shown to hold the asset;
- usage is conflated with demand;
- the asset can be bypassed without degradation;
- evidence appears only as market narrative or community expectation.
7. Common Misreadings
Do not read this checklist as saying:
- usage has no value;
- retained demand is impossible;
- digital assets cannot become infrastructure assets;
- XRP or any asset is automatically rejected;
- XRP or any asset is automatically proven;
- all alternatives are superior;
- all alternatives are costless;
- price can never matter;
- valuation work is useless.
Better reading:
This checklist asks whether visible usage creates durable asset-held demand, and what evidence would be needed before valuation or sizing claims.
8. Relationship to XRP / XRPL / RLUSD
XRP, XRPL, and RLUSD may be used as stress-test cases in the Retained-Demand Audit Series because they raise clear questions about:
- native asset use;
- stablecoin interaction;
- liquidity depth;
- institutional settlement;
- custody;
- collateral;
- market-making;
- Ripple-linked infrastructure;
- operator inventory;
- removal sensitivity.
However:
Ripple success does not automatically imply XRP retained demand.
XRPL progress does not automatically imply XRP retained demand.
RLUSD progress does not automatically imply XRP retained demand.
XRP usage does not automatically imply XRP retained demand.
The relevant question remains:
Who must hold XRP, why, in what role, at what scale, and what worsens if it is removed?
9. Repair Actions for Weak Claims
If a retained-demand claim is weak, possible next steps include:
- identify the actual operator;
- determine whether the asset is selected or merely supported;
- look for inventory, collateral, margin, or liquidity-buffer evidence;
- compare direct routes and alternative routes;
- test removal sensitivity;
- audit institutional friction;
- check usable liquidity depth rather than market cap;
- separate speculative volume from infrastructure demand;
- delay valuation or sizing until evidence gates are addressed.
10. Recommended Short Reference
S. Meta, “Retained-Demand Evidence Checklist,” S. Meta Research Archives, https://s99lab.github.io/