Chainlink aggregator min/max bound misconfig
Rocket Pool's assessment for RD-F-060 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Rocket Pool does not use Chainlink price feeds in any core contract. Confirmed by source inspection of RocketNetworkBalances.sol, RocketNetworkPrices.sol, RocketTokenRETH.sol, and RocketDepositPool.sol — none import any Chainlink interface (AggregatorV3Interface, latestRoundData, latestAnswer). The 19 Chainlink addresses in the data-cache are confirmed pipeline artifacts from a general fee scan unrelated to Rocket Pool.
Sources #
- Curator noteCurator note: Chainlink feeds in data-cache are artifactsData-cache oracle_feeds are pipeline artifacts from general Chainlink feed scan; confirmed not consumed by Rocket Pool contracts per profile §7 oracle noteretrieved 2026-05-04
- RocketNetworkBalances.sol sourceRocketNetworkBalances.sol, RocketNetworkPrices.sol, RocketTokenRETH.sol — no Chainlink import statementsretrieved 2026-05-04
Methodology #
Determine whether the Chainlink aggregator's `minAnswer` and `maxAnswer` circuit-breaker bounds are misconfigured (too wide or too narrow) for the asset class.
See the full factor methodology and distribution across all protocols →