Crypto Due Diligence: A Framework for Claims, Control and Cash Flows

Crypto due diligence is the process of identifying what an asset or service actually promises, who can change those promises, how value is funded and how the user can exit. A useful assessment links each important claim to evidence and records what remains unknown. It does not produce certainty by adding a white paper, an audit badge and a large market capitalization together.

The framework below organizes that work around five records: the asset claim, control rights, economic flows, the exit route and the evidence needed to keep the assessment current. Its purpose is to make a conclusion reproducible and expose the assumptions that could invalidate it.

Define the Decision Before Collecting Information

Research can expand indefinitely unless the decision is explicit. Buying a transferable token, depositing collateral, holding a custodial balance and using a bridge are different actions. They create different claims and different failure paths even when the same brand appears on the interface.

Write one sentence describing the proposed action, the asset involved, the intended use and the condition under which access will be needed. This is a research scope, not a personalized recommendation. A payment workflow requiring same-day availability should investigate different operational constraints from an experiment using a small discretionary balance.

Then identify what would make the action unsuitable for its stated purpose. A missing exit route may be decisive for a time-sensitive payment. Unclear economic rights may be decisive for a token valuation thesis. Beginning with these conditions prevents an attractive narrative from determining which facts receive attention.

Keep price expectations outside the initial fact sheet. A belief that the price will rise does not answer whether the asset is the intended contract, whether the signer has authorized a different action or whether the user can recover access after a service fails.

Record the Exact Asset and the Claim It Represents

Identify the network, contract or asset identifier, issuer where applicable, custody arrangement and relevant documentation. A ticker alone is not sufficient. Different assets can share a symbol, and different routes can produce representations with distinct redemption dependencies.

The ERC-20 standard defines a token interface, including balances and transfers. Compliance with that interface does not itself specify an offchain ownership right, a redemption promise or a claim on a company's profits. Those require separate evidence.

Classify the position in ordinary language. Is it a freely transferable native asset, a claim against an issuer, a receipt for deposited collateral, a governance instrument or a conditional right to a distribution? More than one category may apply, but the overlap should be explained.

For an issuer-backed asset, read the eligibility and redemption conditions. For self-custody, map the signing and recovery arrangement using the principles in cold wallets versus hot wallets. Technical control over a key and legal or operational rights against another party are different layers of the assessment.

Ask Who Can Change the Outcome

List the consequential powers: issuing more tokens, pausing transfers, upgrading contracts, moving treasury assets, changing prices used by a protocol or altering withdrawal conditions. Then identify the account, governance process or organization holding each power.

OpenZeppelin's access-control documentation illustrates the distinction between ownership and role-based permissions. A public contract can still contain privileged operations. The relevant question is what the deployed arrangement permits, not whether its code is visible.

Map the control chain through to the actual authority. A contract owner may be another contract; that contract may be governed by a multisignature arrangement; a separate role may retain upgrade power. A statement that one ownership role was renounced does not answer what other permissions remain.

Record notice periods and exceptions. Who can act immediately in an emergency? Can an ordinary user complete an exit before a proposed change becomes effective? Who decides that the emergency exists? These questions reveal the tradeoff between incident response and discretionary control.

Avoid turning a head count into a probability. Several signing addresses can share one organization, device-management process or recovery dependency. The number of addresses is evidence about the formal arrangement; independence requires additional support.

Trace Every Advertised Return to a Payer

For a yield product, identify the economic source: borrower interest, user fees, a reward for providing resources, a trading strategy, token incentives or transfers from a treasury. A percentage without a payer and an asset denomination is not an adequate description.

Consider a hypothetical vault holding $1 million. Assume its underlying activity produces $75,000 annually, incentive tokens have a reference value of $50,000 and expenses are $20,000. At those assumptions, the net marked result is $105,000, or 10.5% of starting principal.

If the incentive tokens' realizable value falls 60%, the reward component becomes $20,000. With every other input held constant, net value falls to $75,000, or 7.5%. The underlying activity did not need to deteriorate for the headline result to change.

Now introduce a separate hypothetical $40,000 economic loss from the strategy or an asset impairment. The remaining result is $35,000, or 3.5%. These scenarios are arithmetic illustrations, not expected returns or estimated probabilities. They reveal which assumptions contribute to the advertised number.

For a token investment thesis, perform a different reconciliation: which of the protocol's receipts can actually benefit the tokenholder? Protocol revenue and tokenholder value explains why customer payments, treasury accumulation and holder distributions must not be treated as synonyms.

Evaluate the Exit as a Separate Product Feature

A position can appear solvent while being difficult to exit on the required schedule. Determine whether departure means selling on a market, redeeming with an issuer, withdrawing from a contract, waiting through an unbonding process or crossing a bridge.

For each path, record eligibility, expected steps, fees, delays, available liquidity and the party that can interrupt the process. Inspect the fallback when the interface disappears or the usual service is unavailable. A theoretical alternative is less useful if the user lacks the information or capability needed to use it.

For a stablecoin, the market sale and issuer redemption paths can differ. Our analysis of how stablecoins hold their peg explains why a token's target price does not guarantee identical access for every holder.

For a market sale, evaluate depth at a realistic order size. Liquidity and trading volume answer different questions; past turnover is not a promise of present execution capacity. The assessment should preserve both the normal route and the route available under stress.

Build an Evidence Register, Not a Badge Collection

Classify each important statement as observed, documented but not independently confirmed, inferred, unknown or contradicted. These statuses are not a scientific risk score. They help the reader see the difference between an accessible fact and a confident presentation.

An issuer's terms are a primary source for its stated conditions, not independent proof that every operational promise will always be fulfilled. An onchain balance proves a balance under the chosen observation, not necessarily beneficial ownership or the absence of offsetting obligations. The limits of proof of reserves and audits are especially important here.

Keep sources next to claims, including their dates or versions. A collection of impressive links at the bottom of a report is weaker than a clear record of which proposition each source actually supports.

Check Whether the Audit Matches the Position

Read the audit's scope, inspected commit or version, unresolved findings, exclusions and assumptions. Compare those with the deployed implementation and the dependencies used by the product. A report on a different contract or an earlier configuration may provide useful history without validating the current arrangement.

Ethereum's smart-contract security guidance describes audits as an additional review rather than a guarantee that every bug has been found. Testing, operational controls and changes after the review remain relevant.

A vault can also combine several reviewed components in a new way. Their interaction may create a risk absent from any single report. Follow the actual asset path through oracles, bridges, administrators and underlying strategies, then identify which interactions were within the review scope.

For a product deployed on a rollup, include layer-2 validation, upgrade and exit risks. A correct application transaction can still depend on infrastructure behavior outside the application's own audit.

Use Stress Scenarios to Reveal Hidden Dependencies

Choose scenarios that change constraints rather than merely lowering every asset price by the same percentage. What happens if the usual exchange stops accepting deposits, a collateral price feed becomes unavailable, an issuer restricts redemptions for a particular account class or an administrator loses access?

For each scenario, write the first failed assumption, the remaining exit route and the evidence that route works. If the response relies on the same party or infrastructure that caused the initial problem, the apparent backup may not be independent.

Distinguish temporary loss of access from economic impairment. A position can survive intact but miss a payment deadline. Another can remain transferable while its backing loses value. Both matter, but describing them as the same risk produces a less useful response plan.

Supply changes deserve their own scenario. Token unlocks and FDV can alter the ownership denominator or tradable inventory without specifying how price responds. Model the changing claim before adding a speculative market reaction.

State the Strongest Countercase

A conservative assessment can also go wrong by treating every unknown as proof of failure. Some documentation gaps are repairable, some restrictions are explicit design choices, and some users may accept a limitation for a narrow purpose. The right conclusion depends on the requirement established at the beginning.

The countercase should still be specific. If concern centers on withdrawal concentration, what evidence of a robust alternative would change the conclusion? If concern centers on incentive dependence, what pattern of retained usage would support durable demand? If an active revenue mechanism is missing, which implemented change would establish it?

Likewise, a positive assessment needs a failure condition. A newly introduced administrator, a changed contract, a different bridge route or a revised redemption policy can invalidate an earlier conclusion without any dramatic price movement. Research that cannot be updated when facts change is a narrative, not a control process.

Keep a Short Decision Record

Finish with a compact record of the proposed action, supported claims, material uncertainties, exit requirements and triggers for reassessment. Attach the source register and calculations. A second reader should be able to see which conclusions follow from evidence and which remain conditional.

Do not compress everything into an unsupported safety percentage. A strong balance sheet does not cancel an uncontrolled signing key; a useful product does not create tokenholder rights that are absent; a successful small withdrawal does not establish unlimited future liquidity. These risks interact but are not interchangeable points in a score.

The continuing work is to monitor changes that matter to the original decision. Review new contract versions, privileged roles, supply rules, distribution mechanisms and exit conditions. That creates a practical form of due diligence: a clear explanation of what is being relied upon today, and a defined reason to revisit it tomorrow.