External keeper/relayer not redundant
Circle USYC'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 reporter (immutable _reporter = 0x9fde717a21c5b272B8956d3AA0c3551E1FFd23D7 in GenericNextPriceAggregator) is functionally a single-keeper push oracle. If this address fails to transmit, prices go stale. No redundancy mechanism or failover identified. The Teller has setOracle (ABI confirmed) allowing oracle contract swap, but within the current live oracle contract the reporter is immutable. Single-keeper dependency without redundancy confirmed.
Sources #
- EtherscanTeller Implementation ABI - EtherscanTeller implementation at 0xF8724D6b9E6fF55Bc4496fddb3437DC691CD26EB - setOracle function present (admin can swap oracle contract) but no redundancy mechanismretrieved 2026-05-16
- GenericNextPriceAggregator Oracle Implementation - EtherscanGenericNextPriceAggregator at 0x6DeaA761bc131Ac5f1D562EE71819E846EF11624 - immutable address _reporter = 0x9fde717a21c5b272B8956d3AA0c3551E1FFd23D7; sole transmitterretrieved 2026-05-16
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 →