Dependency graph (protocols depended upon)
Balancer (v2 + v3)'s assessment for RD-F-050 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
External dependency graph is well-understood. v2 key deps: Aave v2/v3 (aToken rate for Boosted Pools), Lido/wstETH (stEthPerToken()), ERC-4626 vault contracts (Linear Pool wrappers), Chainlink (optional ChainlinkRateProvider). v3 key deps: Aave v3 ERC-4626 (Boosted Pools), hook contracts (per-pool), Permit2 (router). All deps are highly reliable protocols (Aave, Lido). Dependency scope is per-pool — a failure in one rate provider does not cascade to the global Vault. The Vault itself (v2 0xBA12222... v3 0xbA13333...) has no external oracle dependency for core operations.
Detail #
v2 architecture separates pool logic from token accounting — the Vault holds all tokens, and pools communicate rates, not prices. This limits blast radius of rate provider failure to the specific pool. v3 further formalizes this separation. Aave partnership confirmed as primary Boosted Pool dependency for both v2 and v3.
Sources #
- DocsBoosted Pools | Balancer v2Balancer v2 Boosted Pools — Aave and ERC-4626 dependency descriptionretrieved 2026-05-05
- Balancer v3 launches with Aave partnership | The Blockv3 launch with Aave Boosted Pool partnershipretrieved 2026-05-05
Methodology #
List all external protocols whose failure would directly impair this protocol (LST providers, bridges, stablecoin issuers, keepers).
See the full factor methodology and distribution across all protocols →