Fast answer
DeFi yield checks need APY source, protocol, contract exposure, liquidity, oracle risk, governance controls, fees, and exit route.
Before using a DeFi yield strategy, record the chain, protocol, contract address, asset, yield source, risk parameters, liquidity depth, oracle source, governance controls, fee path, and exit transaction.
No guaranteed yield exists; staking, lending, liquidity provision, and reward programs all need lockup, smart-contract, market, liquidity, tax, and withdrawal-risk checks.
Yield checks
What to inspect before a DeFi yield claim is reviewable.
Yield source
Identify whether the return comes from lending demand, trading fees, emissions, staking rewards, points, or subsidies.
Protocol controls
Record risk parameters, caps, pause controls, governance rules, and admin or upgrade paths.
Liquidity depth
Thin liquidity can make exit costs larger than expected yield.
Oracle and contract risk
Price feeds, contract bugs, bridges, and token approvals can change the final result.
Source context
Aave, Compound, and Uniswap docs all show that DeFi yield depends on changing risk parameters and pool mechanics.
CSR keeps DeFi yield content framed as risk review and recordkeeping, not as a return recommendation.
Review standard
A reviewable DeFi yield record proves where returns came from and how the position exits.
For CSR evidence review, DeFi Yield Risk Guide records should preserve asset, chain, protocol, wallet or exchange, reward source, fee, lockup or withdrawal rule, smart-contract exposure, slashing or liquidation rule, transaction hash, and final outcome.