defirisk.co
rubric v1.7.0

External keeper/relayer not redundant

Across Protocol'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 #

Relayer redundancy: protocol is permissionless for relayers (any party can run a relayer); bridge fills are permissionless. Dataworker (bundle proposer) is more centralized — Risk Labs runs the primary dataworker, though the permissive design allows anyone to propose. If the single dataworker is offline, no new bundles are proposed; relayers bear capital risk indefinitely until someone proposes. Dataworker is NOT redundant in practice.

Sources #

  • Curator note
    Extracted from 03-oracle-deps.md — RD-F-062 finding; no URL cited in originalretrieved 2026-04-28

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 →

rubric_version v1.7.0 protocol across-protocol factor RD-F-062 score yellow collected_at 2026-04-30 21:19:18