Dependency graph (protocols depended upon)
stHYPE (Valantis Labs)'s assessment for RD-F-050 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Critical non-redundant dependencies: (1) Hyperliquid HyperCore L1 validator set — existential, non-EVM, non-inspectable; (2) 5 standard HyperCore Staking Modules — hold HYPE custody; (3) HIP-3/HyENA module — Ethena-linked, HIP-3 slashing mechanics; (4) USDe quote-asset module — novel permissionless spot quote asset slashing. Secondary: REBASER_ROLE keeper (single address, liveness); STEX AMM (instant-unstake only, not core path). Yellow because HyperCore modules are non-inspectable existential dependencies with no redundancy or fallback path.
Sources #
- DocsstHYPE Roles and Controls Registryroles-and-controls-registry — REBASER_ROLE held by single address 0x4eb038eb501045daa520b972fcad48c429531e10retrieved 2026-05-17
- stHYPE Stake AccountsValantis stake-accounts page confirming 7 stake accounts and allocation strategyretrieved 2026-05-17
- stHYPE Transparency and RisksValantis transparency-and-risks page listing 5 standard modules + HIP-3 + USDe module; slashing exposure per module typeretrieved 2026-05-17
Methodology #
List all external protocols whose failure would directly impair this protocol (LST providers, bridges, stablecoin issuers, keepers).
See the full factor methodology and distribution across all protocols →