Breakage analysis per dependency
stHYPE (Valantis Labs)'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 #
Breakage per dependency: HyperCore L1 halt → all staking operations cease, ~$144M TVL stranded in unbonding; HIP-3 slashing → partial NAV loss + extended withdrawals; USDe module slashing → partial NAV loss (novel model); REBASER_ROLE keeper offline → rebase stale, no capital loss; STEX AMM illiquid → instant-unstake unavailable, standard path unaffected. Yellow because breakage analysis is partially complete — HyperCore module allocation percentages (needed to quantify partial-slashing impact) are not accessible from HyperEVM.
Sources #
- DocsstHYPE Transparency and Riskstransparency-and-risks listing slashing risk per module type and withdrawal timeline impactsretrieved 2026-05-17
- stHYPE Roles and Controls Registryroles-and-controls-registry confirming REBASER_ROLE is single address with no redundancy documentedretrieved 2026-05-17
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 →