Breakage analysis per dependency

Evidence summary #

Yearn's official protocol risk documentation (docs.yearn.fi/developers/security/risks/protocol-risks) documents per-protocol-type failure modes for all major dependencies: lending (liquidation failures, oracle errors, smart contract risk), AMMs (liquidity shortages, impermanent loss, fee reduction), leverage protocols (collateralization failures, oracle-driven liquidation). However, the analysis is category-level, not per-strategy or per-dependency severity matrix. Historical incidents (2021 Curve manipulation yDAI, 2023 Fulcrum misconfiguration yUSDT) confirm that breakage analysis was insufficient pre-incident. Current documentation is substantially improved. Yellow: documented at category level but not structured as per-dependency severity map.

Sources #

Methodology #

Produce a short per-dependency text describing which protocol functions halt or degrade and impact severity if each declared dependency fails.

See the full factor methodology and distribution across all protocols →