Oracle role per asset
Fluid'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 #
For each vault, the oracle serves as Primary for collateral pricing and liquidation. The FallbackCLRSOracle (now deprecated, replaced by GenericOracle) explicitly supports Chainlink-primary/Redstone-fallback or Redstone-primary/Chainlink-fallback modes (3 modes: 1=CL only, 2=CL primary RS fallback, 3=RS primary CL fallback). The GenericOracle supports up to 4 oracle hops chained sequentially. DEX Smart Collateral vaults use dexSmartColCLOracle (Chainlink + DEX reserves). However, specific asset-to-oracle-mode mappings across all 20+ vault configurations are not fully enumerated in available sources — the oracle type per vault requires individual vault state reads. Yellow because the system supports defined primary/fallback roles but complete per-asset enumeration was not achievable without chain reads across all vault instances.
Sources #
- GitHubFluid FallbackCLRSOracle (deprecated) sourceInstadapp/fluid-contracts-public/contracts/oracle/oracles/fallbackCLRSOracle.sol — mainSource_ modes 1/2/3retrieved 2026-04-29
- Fluid GenericOracle sourceInstadapp/fluid-contracts-public/contracts/oracle/oracles/genericOracle.sol — up to 4-hop configurationretrieved 2026-04-29
- Fluid DEX Smart Collateral Chainlink OracleInstadapp/fluid-contracts-public/contracts/oracle/oracles/dex/dexSmartColCLOracle.solretrieved 2026-04-29
Methodology #
For each oracle, classify its role as Primary / Secondary / Fallback per asset/market.
See the full factor methodology and distribution across all protocols →