Fallback behavior on oracle failure
Liquid Collective (LsETH)'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 #
No fallback oracle identified. Oracle.1.sol source contains no try/catch around oracle calls, no secondary data source, no last-known-price mode. When quorum is not reached, the protocol continues operating on the previously-accepted rate (rate freezes). The epoch-age check (EpochTooOld) prevents submission of stale-epoch reports but does not trigger a fallback. No emergency oracle mechanism documented.
Sources #
- DocsLiquid Collective Architecture Docs24-hour reporting cadence; no fallback mechanism describedretrieved 2026-05-17
- Liquid Collective Oracle.1.sol sourceOracle.1.sol — no fallback logic; if quorum not reached, no action; epoch check onlyretrieved 2026-05-17
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 →