Breakage analysis per dependency
Kinetiq'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 analysis: (1) HyperCore L1 halts → StakingManager L1Write calls revert → no new stakes/unstakes; reward settlement stops; exchange rate freezes at last value. (2) Operator stops → validator performance scores go stale; StakeHub rebalancing stops; bad validators may hold delegations beyond intended period. (3) Malicious DefaultOracle adapter authorized → false performance scores elevate compromised validators → yield theft. (4) OracleManager fully paused → all performance updates halt; rate computation continues on stale inputs. Yellow because these are known risks acknowledged in docs/audits, not undisclosed. Primary source: Code4rena README audit scope + StakingManager.sol L1Write pattern.
Sources #
- GitHubKinetiq Code4rena Audit READMECode4rena audit README: 'The OPERATOR_ROLE must reliably execute L1 operations and manage the operation queue' — failure mode acknowledged; StakingManager.sol L1Write dependencyretrieved 2026-05-17
- Kinetiq FAQKinetiq FAQ: 'Hyperliquid currently has no slashing' — confirms L1 dependency risk acknowledged by teamretrieved 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 →