External keeper/relayer not redundant
Hyperlane'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 #
Hyperlane off-chain relayer network is Abacus Works operated for default routes. The Mailbox.process() call is permissionless (anyone can submit), but the primary relayer infrastructure is centralized. IGP StorageGasOracle updates are owner-only (no keeper). No Chainlink Automation or Gelato dependency found in core path. Relayer centralization is a liveness risk but not a fund-loss risk (permissionless process() allows self-relay as fallback).
Sources #
- InternalHyperlane profile §7 — external dependencies00-profile.md §7 — relayer infrastructure operated by Abacus Works for default ISM routesretrieved 2026-05-17
- Mailbox.sol — permissionless process()Mailbox.sol — process() is permissionless (no msg.sender check); anyone can submit valid messagesretrieved 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 →