Oracle role per asset

Lido's assessment for RD-F-049 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

AccountingOracle = Primary for stETH rebase; ValidatorsExitBusOracle = Primary for exit requests. No secondary or fallback oracle. If committee fails quorum, rebase halts and exit processing stalls.

Detail #

Docs confirm: 'Oracle daemons could stop pushing their reports for extended periods of time in case of no finality on the Ethereum Consensus Layer.' No fallback oracle by design. Yellow because no fallback documented or implemented.

Sources #

Docs
https://docs.lido.fi/contracts/accounting-oracleretrieved 2026-04-28
Docs
https://docs.lido.fi/contracts/validators-exit-bus-oracleretrieved 2026-04-28

Methodology #

For each oracle, classify its role as Primary / Secondary / Fallback per asset/market.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol lido factor RD-F-049 score yellow collected_at 2026-04-28 13:58:42