External keeper/relayer not redundant
stHYPE (Valantis Labs)'s assessment for RD-F-062 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Single REBASER_ROLE keeper at 0x4eb038eb501045daa520b972fcad48c429531e10. Only one address holds REBASER_ROLE per roles-and-controls-registry. No redundant keeper or permissionless rebase path documented in ABI or docs. If keeper goes offline, rebases stop; stHYPE ceases to accrue rewards until DEFAULT_ADMIN_ROLE Safe grants REBASER_ROLE to a new address. Fund custody unaffected. Yellow: single non-redundant liveness keeper.
Sources #
- DocsstHYPE Roles and Controls Registryroles-and-controls-registry: Overseer REBASER_ROLE = 0x4eb038eb501045daa520b972fcad48c429531e10 (single address)retrieved 2026-05-17
- OverseerV1 ABIoverseerV1.json ABI — rebase(uint256 l1Balance) is a privileged call; no permissionless rebase function foundretrieved 2026-05-17
Methodology #
Determine whether the protocol depends on a single keeper or relayer (Gelato, Chainlink Automation, custom) with no redundancy or failover.
See the full factor methodology and distribution across all protocols →