Fallback behavior on oracle failure
Beefy Finance's assessment for RD-F-051 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
BeefyOracle uses single sub-oracle per token with no fallback — if sub-oracle fails (success=false), stale price remains. BeefySwapper returns (0, false) on price failure with no documented secondary source fallback. CLM reverts deposits if TWAP unavailable (fail-safe behavior). No secondary oracle configured for any asset in the system. Yellow because CLM has fail-safe revert (better than accepting bad data) but no positive fallback.
Sources #
- GitHubBeefyOracle.sol — oracle failure behaviorBeefyOracle.sol — 'if sub-oracle price update fails (success=false), stale price remains unchanged'retrieved 2026-05-16
- BeefySwapper.sol — oracle failure handlingBeefySwapper.sol — returns (0, false) on getFreshPrice failureretrieved 2026-05-16
Methodology #
Identify the declared fallback behavior (pause, secondary source, last-known-price, revert) when the primary oracle reverts or reports a stale value.
See the full factor methodology and distribution across all protocols →