Single-pool oracle (no medianization)
Fluid's assessment for RD-F-056 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
For most vault configurations, Chainlink feeds are the single source (no medianization across multiple venues). The FallbackCLRSOracle (deprecated) provides Chainlink + Redstone fallback in certain modes, which is effectively dual-source sequential (not medianized). The GenericOracle chains up to 4 hops sequentially — if one hop uses Chainlink and another uses Redstone, they are sequentially composed, not medianized. The UniV3Check oracle (deprecated) performed a delta-check against Chainlink rather than medianizing. Medianization across multiple venues is NOT present. Yellow because the fallback provides some multi-source coverage but it is sequential fallback, not true medianization.
Sources #
- GitHubFluid FallbackOracleImpl architectureInstadapp/fluid-contracts-public/contracts/oracle/implementations/fallbackOracleImpl.sol — sequential fallback, not medianizedretrieved 2026-04-29
Methodology #
Determine whether the oracle reads from a single DEX venue with no medianization across multiple pools or venues.
See the full factor methodology and distribution across all protocols →