Fallback behavior on oracle failure
Yearn 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 #
Vault core (V2 + V3): no oracle to fail; fallback not applicable to vault pricePerShare. Strategy-level: V3 TECH_SPEC confirms no staleness checks or fallback oracle mechanism at spec level. Strategy writing guide warns about oracle manipulation risk but does not mandate fallback behavior. V2 BaseStrategy baseFeeOracle failure: harvest reverts until admin updates via setBaseFeeOracle(). No documented fallback to secondary oracle or last-known-price at strategy framework level. Individual strategies may implement their own fallbacks, but this is not systematically verified. Yellow: no uniform fallback; vault core unaffected; strategy-level is undefined at framework level.
Sources #
- GitHubYearn V3 Technical SpecificationTECH_SPEC.md: no staleness checks or oracle fallback mechanism describedretrieved 2026-05-16
- Yearn V3 Strategy Writing GuideStrategy writing guide: warns on oracle manipulation but no fallback mandateretrieved 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 →