Fallback behavior on oracle failure

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

ResilientOracle has explicit try-catch cascade: Main fails → fallback vs pivot. All fail → revert. Individual adapter level (SlisBnbOracle, BnbOracle) has NO staleness check — delegates entirely to ResilientOracle. Lista Lending markets have no protocol-level fallback; market oracle failure halts that market. Yellow because adapter-level staleness absent and Lista Lending fallback is none.

Sources #

GitHub
Lista DAO ResilientOracle.solcontracts/oracle/ResilientOracle.sol — _getPrice() try-catch structure; contracts/oracle/SlisBnbOracle.sol — no adapter-level fallbackretrieved 2026-05-12
GitHub
Lista DAO SlisBnbOracle.solcontracts/oracle/SlisBnbOracle.sol — delegates to constant ResilientOracle without staleness checkretrieved 2026-05-12

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 lista-dao factor RD-F-051 score yellow collected_at 2026-05-12 17:54:05