Fallback behavior on oracle failure
Usual (USD0 / bUSD0 / USUAL)'s assessment for RD-F-051 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No fallback oracle for any collateral asset. ClassicalOracle has a single data source per token (one Chainlink/Hashnote feed). If USYC NAV oracle reverts or returns stale data, no secondary source is consulted. CBR (Collateral Backing Ratio) is admin-activatable but requires human intervention — it is NOT an automatic oracle fallback. When ClassicalOracle fails, the minting/redeeming path halts with no degraded-mode backup.
Sources #
- EtherscanDaoCollateral Implementation — EtherscanDaoCollateral ABI: activateCBR/deactivateCBR are admin-callable functions — no automatic fallback in contract interfaceretrieved 2026-05-17
- ClassicalOracle | Usual Tech Docstech.usual.money ClassicalOracle: 'interacts with the aggregator to fetch the latest price' — singular aggregator per token, no fallback describedretrieved 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 →