External keeper/relayer not redundant
Kinetiq'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 Operator contract (0x23A4604cDFe8e9e2e9Cf7C10D7492B0F3f4B4038) serves as sole keeper: calls GeneratePerformance on OracleManager and CompleteReward on StakingManager daily. No documented redundant keeper, Gelato automation backup, or Chainlink Automation redundancy found in docs or source. 11,663 transactions indicates continuous operation historically, but single-point-of-failure design. If Operator key is compromised or the contract halts, validator performance updates and reward accrual stop with no alternative keeper.
Sources #
- EtherscanKinetiq kHYPE Operator — HyperEVMScanOperator 0x23A4604cDFe8e9e2e9Cf7C10D7492B0F3f4B4038 — 11,663 txs, labeled 'Kinetiq: kHYPE Operator', automated contract, single address calling GeneratePerformanceretrieved 2026-05-17
- Kinetiq Contracts and Auditskinetiq.xyz/docs/contracts-and-audits: one Operator contract listed, no backup keeper documentedretrieved 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 →