Fallback behavior on oracle failure
Lido'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. If oracle committee fails quorum, stETH rebase halts for the frame. Docs explicitly state daemons may stop reporting during ETH consensus non-finality. No automatic secondary source or last-known-price fallback.
Detail #
Protocol docs: 'Oracle daemons could stop pushing their reports for extended periods of time in case of no finality on the Ethereum Consensus Layer. This would ultimately result in no oracle reports and no stETH rebases for this whole period.' GateSeal provides emergency pause but not automatic fallback.
Sources #
- Docshttps://docs.lido.fi/contracts/accounting-oracleretrieved 2026-04-28
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 →