DeFi Risk Checklist

Trace contracts, control, liquidity, oracles, bridges, and exit assumptions before interacting.

Reviewed September 10, 2026

Quick answer

A DeFi position is a dependency chain. Identify the network, contracts, administrative controls, oracle, liquidity, token approvals, bridged assets, interface, and exit path. A high yield or completed audit does not remove these dependencies.

At a glance

  • Smart-contract audits are evidence of review, not guarantees.
  • Oracle inputs have source, timing, aggregation, and governance assumptions.
  • Bridged assets depend on additional verification or custody systems.
  • Headline yield should be decomposed into fees, emissions, token price exposure, and withdrawal costs.

Step-by-step walkthrough

  1. Write down the network, protocol, contract addresses, and interface domain.
  2. Identify upgrade, pause, mint, freeze, multisig, and emergency powers.
  3. Record oracle providers and what happens when data becomes stale or unavailable.
  4. Inspect liquidity, withdrawal rules, lockups, incentives, and likely slippage under stress.
  5. Identify bridged or wrapped assets and the system backing each representation.
  6. Find audits, bug bounties, incident history, and a public emergency communication channel.
  7. Define how to revoke approvals and exit if the primary interface is unavailable.
Worked scenario · illustrative values

A 20% advertised yield

The number becomes meaningful only after its components and dependencies are identified.

SignalWhat it can meanImportant caveat
5% trading feesDepends on volume and provider share.Volume and pool share can change.
15% token incentivesPaid through new or treasury tokens.Token price and emissions may fall.
Audited contractsA defined review occurred.Economic, oracle, bridge, and new-code risks remain.

Common mistakes and edge cases

  • Treating total value locked as a safety score.
  • Assuming “non-custodial” means no governance or key-holder risk.
  • Ignoring token approvals, bridge dependencies, or oracle failure modes.
  • Comparing yields without matching time periods, token units, and exit costs.

Reusable checklist

Checklist selections are temporary and are not transmitted or treated as a safety score.