Fallback behavior on oracle failure
Stake DAO'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 #
Core locker path: oracle-free — no oracle failure mode. Morpho lending vault path: BaseOracle.sol enforces revert-on-stale (require(latestPrice > 0 && updatedAt > block.timestamp - maxStale)). Fallback behavior is HALT (revert), not secondary oracle or last-known-price. No secondary oracle feed configured in adapters. Yellow: revert-on-stale is better than ignoring stale prices; lacks secondary oracle fallback.
Sources #
- GitHubBaseOracle.sol fallback = revert on stalepackages/periphery/src/lending/oracles/BaseOracle.sol — _fetchFeedPrice() revert pattern: require(latestPrice > 0 && updatedAt > block.timestamp - maxStale, InvalidPrice())retrieved 2026-05-16
- Stake DAO lending oracle documentationdocs.stakedao.org/lending/oracles — staleness check described; no secondary fallback oracle mentionedretrieved 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 →