External keeper/relayer not redundant
USDD (Decentralized USD)'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 #
The oracle system requires periodic price pushes from Chainlink and WINkLink oracle nodes. If oracle nodes stop posting, the Median receives no new valid prices and OSM freezes. The ChainSecurity Jan-2025 audit recommended 'active monitoring' of oracle correctness — suggesting no automated keeper fallback is implemented. Dual oracle providers (Chainlink + WINkLink) provide partial redundancy but the governance delay is currently disabled, reducing the human-intervention window.
Sources #
- AuditPUBLIC Code Assessment of USDD V2 Smart Contracts, January 24 2025ChainSecurity USDD V2 audit Jan 2025: 'active monitoring is required to ensure the oracle and governance work correctly' — no automated keeper/relayer redundancy mentionedretrieved 2026-05-17
- USDD Oracle Developer DocsDual oracle providers (Chainlink + WINkLink) provide partial keeper redundancy; details of node count not 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 →