Breakage analysis per dependency
Euler V2's assessment for RD-F-052 — scored not_assessed on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
[downgraded: only curator_note evidence] Per-dependency breakage: Chainlink feed stale → vault borrow/liquidation halts (vault-specific, not protocol-wide). USDT/USD has 86400s (24h) heartbeat — up to 24h stale data before revert. Pyth failure → Pyth-oracle vaults halt. UniswapV3 manipulation → over-borrowing against manipulated collateral. Lido failure → wstETH-vaults misprice. EVC bug → all vaults on that chain affected (no recovery path). Partial analysis; full breakage mapping requires per-vault oracle enumeration not completed here.
Sources #
- Curator noteEuler V2 Oracle Dependency Breakage AnalysisDependency graph analysis from profile §7 and oracle adapter source reviewretrieved 2026-05-04
Methodology #
Produce a short per-dependency text describing which protocol functions halt or degrade and impact severity if each declared dependency fails.
See the full factor methodology and distribution across all protocols →