Chainlink aggregator min/max bound misconfig
Morpho V1 (Morpho Blue + MetaMorpho)'s assessment for RD-F-060 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
ChainlinkOracleV2 does not check minAnswer/maxAnswer bounds — delegates to Chainlink aggregator internal circuit breakers. Cannot fully assess per-feed bounds without per-feed on-chain reads. High-priority feeds (ETH/USD, BTC/USD) generally have reasonable bounds; exotic/custom feeds in permissionless markets may not.
Detail #
Data cache provides feed addresses but not minAnswer/maxAnswer values. MorphoChainlinkOracleV2 source does not implement minAnswer/maxAnswer checks — it uses ChainlinkDataFeedLib which only extracts answer. Chainlink feeds (ETH/USD 0x5f4eC3Df9cbd43714FE2740f5E3616155c5b8419, BTC/USD 0xF4030086522a5bEEa4988F8cA5B36dbC97BeE88c) on Ethereum mainnet typically have non-default bounds, but this has not been verified on-chain. Template: yellow when bounds wider than historical 2x swing.
Sources #
- EtherscanChainlink ETH/USD Ethereum — EtherscanChainlink ETH/USD feed 0x5f4eC3Df9cbd43714FE2740f5E3616155c5b8419retrieved 2026-04-27
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 →