Fallback behavior on oracle failure
Concrete's assessment for RD-F-051 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No oracle is used in Concrete's vaults, so oracle-failure fallback design is not applicable in the traditional sense. For strategy yield accounting, the cached totalAssets state is updated pre-operation by _accrueYield(); if a strategy's totalAllocatedValue() returns stale data, the vault uses cached state which does not auto-correct. No explicit circuit breaker on strategy yield reporting is present, but this is a strategy-failure risk (scored under F052), not an oracle-failure-fallback gap.
Sources #
- GitHubConcrete Architecture.md — vault accounting modeldoc/Architecture.md — cached totalAssets model; _previewAccrueYieldAndFees() aggregates strategy yieldsretrieved 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 →