Chainlink aggregator min/max bound misconfig
StakeWise v3'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 #
StakeWise does not consume any Chainlink aggregator feeds in its core oracle path. The PriceFeed contract mimics the Chainlink AggregatorV3Interface but IS the adapter, not a Chainlink consumer. Chainlink's ETH/USD feed is consumed only by Aave's external CAPO adapter (outside StakeWise's contracts). Factor applies to protocols that consume Chainlink feeds where minAnswer/maxAnswer misconfiguration is possible.
Sources #
- EtherscanPriceFeed — Etherscan sourcePriceFeed source: implements Chainlink interface but does not call any Chainlink aggregator; reads OsTokenVaultController.getRate() onlyretrieved 2026-05-16
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 →