Role separation: upgrade ≠ fee ≠ oracle
stHYPE (Valantis Labs)'s assessment for RD-F-035 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
FEE_RECIPIENT_ROLE (0xa2666b4dd) and MANAGER_ROLE (0x53D6c6594d) are distinct from the admin Safe. REBASER_ROLE (0x4eb038eb) distinct from Safe. However, upgrade role and PAUSER_ROLE are held by the same Safe — no upgrade/pause separation. Two of three pairs are separated; upgrade=pause is not.
Sources #
- DocsstHYPE Roles and Controls Registrydocs.valantis.xyz/stakedhype/roles-and-controls-registry — full role table showing MANAGER_ROLE=0x53D6c6594d, FEE_RECIPIENT_ROLE=0xa2666b4dd, REBASER_ROLE=0x4eb038eb; all distinct from Safe; but PAUSER_ROLE=Safe, DEFAULT_ADMIN/ProxyAdmin=Saferetrieved 2026-05-17
Methodology #
Determine whether the upgrade role, fee-collection role, and oracle-config role are assigned to distinct addresses.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol staked-hype factor RD-F-035 score yellow collected_at 2026-05-17 13:02:38