External keeper/relayer not redundant

Evidence summary #

ORDER_KEEPER role in RoleStore gates all order execution. Keepers are team-controlled whitelisted addresses (not permissionless). If keeper network goes offline or is compromised, all order execution halts — no permissionless fallback. GMX docs known-issues confirms keeper downtime prevents execution. Multiple keeper addresses likely exist but all are team-controlled (centralized operator set). L2 sequencer check is not automated for non-atomic actions per docs.

Detail #

Profile §7: ORDER_KEEPER role whitelisted in RoleStore; 'likely team-controlled'. GMX known-issues page acknowledges keeper liveness dependency. OracleStore.sol manages signer set. Keeper addresses not enumerated on-chain in this assessment (deferred to governance-admin-analyst). Template: yellow = single keeper provider (team-controlled), protocol function halts on keeper failure.

Sources #

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 →