External keeper/relayer not redundant
dYdX v4 (dYdX Chain)'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 #
Slinky sidecar is functionally a keeper/relayer for oracle price submission, but is redundantly operated — every validator must run it (mandatory from v5.0.0). With 60+ active dYdX Chain validators, no single keeper can be taken down. However, Skip Protocol is the sole maintainer of the Slinky library — a supply-chain concentration risk. A malicious or buggy Slinky library update could affect oracle consensus across all validators simultaneously.
Sources #
- DocsRunning a Validator — dYdX DocsValidator docs: Slinky mandatory for all validators from v5.0.0retrieved 2026-05-17
- dydxprotocol/slinky — GitHubslinky repo: maintained by Skip Protocol / dydxprotocol — sole software library for validator oracleretrieved 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 →