Oracle role per asset
Balancer (v2 + v3)'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 #
Single rate provider per yield token per pool in both v2 and v3. No secondary or fallback oracle at the protocol level. v2 ComposableStablePool: one rate provider per token slot (primary only). v3: one rate provider per token slot at pool registration (immutable post-registration). The v3 Geomean Oracle Hook uses no fallback oracle. No protocol-defined failover exists if the primary rate provider fails.
Detail #
Template: yellow = primary only with no fallback documented. The lack of fallback is a deliberate architectural choice (rate providers return a single authoritative rate from the yield protocol). This is common for AMM rate-provider designs but represents elevated risk if Aave or wstETH contracts become unavailable.
Sources #
- DocsRate Providers | Balancer v3v3 rate provider docs — single rate provider per token slot, immutable at registrationretrieved 2026-05-05
- Rate Providers | Balancer v2v2 rate provider docs — single getRate() per token, no fallbackretrieved 2026-05-05
Methodology #
For each oracle, classify its role as Primary / Secondary / Fallback per asset/market.
See the full factor methodology and distribution across all protocols →