Fallback behavior on oracle failure

Maple 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 #

On primary Chainlink feed staleness: contract reverts (MG:GLP:STALE_PRICE). Governor can call setManualOverridePrice() to unblock — human-triggered, not automatic. No automatic fallback to secondary oracle. Aave/Sky strategy failures contained — idle liquidity stays in pool.

Detail #

MapleGlobals getLatestPrice() reverts if updatedAt < block.timestamp - maxDelay. No automated secondary oracle fallback in the code path. setManualOverridePrice() available as emergency measure but requires governor action. Yellow because revert-on-staleness with human-triggered override is a documented but non-automatic fallback pattern.

Sources #

GitHub
MapleGlobals sourceMapleGlobals.sol getLatestPrice staleness check and setManualOverridePriceretrieved 2026-04-27

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 →

rubric_version v1.7.0 protocol maple-finance factor RD-F-051 score yellow collected_at 2026-04-27 05:38:08