Breakage analysis per dependency
Beefy Finance's assessment for RD-F-052 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Partial breakage analysis available: CLM TWAP manipulation risk documented (deposits revert on manipulation; Zellic critical tick-math finding was fixed pre-deployment). BeefySwapper oracle stale price risk: harvest quality degrades but vault principal unaffected. Wrapped protocol failure: vault-specific panic() available; documented in SAFU practices. BIFI bridge adapter failure: other three paths remain. Full enumeration of all wrapped protocols not available without programmatic sweep. Yellow because major dependencies are covered but not exhaustive.
Sources #
- DocsBeefy BIFI Token Bridge documentationToken bridge docs — 4 adapters provide redundancy; single adapter failure does not halt bridgingretrieved 2026-05-16
- Beefy SAFU Practices — panic mechanismSAFU practices: panic() function withdraws staked funds from farm to strategy contract on emergencyretrieved 2026-05-16
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 →