Breakage analysis per dependency
Lido'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: oracle offline halts rebase; Beacon Chain non-finality halts oracle + exits; DAO capture enables false oracle committee changes. No formal published breakage-analysis documentation found.
Detail #
Breakage scenarios identified via source inspection and docs review. No dedicated public breakage analysis document found. Yellow because major deps covered in profile §7 and docs but no protocol-published formal dependency-failure analysis.
Sources #
- InternalLido profile §7 breakage flagsretrieved 2026-04-28
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 →