Fallback behavior on oracle failure
Lombard 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 #
StakedLBTCOracle reverts on consortium proof failure with no fallback to alternative source (source inspection: no try/catch or secondary oracle path found). PoR oracle has no staleness fallback; cadence is 10-minute push per docs. Lombard's LBTC minting is Consortium-authorized (not price-oracle gated), so BTC/USD oracle failure does not directly block minting — it affects downstream lending consumers. No try/catch oracle fallback logic found in StakedLBTCOracle or PoR contract source. Yellow: reverts rather than graceful degrade on oracle failure; no declared fallback source.
Sources #
- GitHub
- Lombard StakedLBTCOracle sourceStakedLBTCOracle.sol — revert on proof failure, no fallbackretrieved 2026-05-05
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 →