Chainlink aggregator min/max bound misconfig
Maple Finance'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 #
Chainlink aggregators include minAnswer/maxAnswer bounds set by Chainlink. MapleGlobals does not independently verify these bounds. Known risk: if collateral asset crashes below minAnswer, feed returns minAnswer (floor), not real price. Cannot verify all bound configurations without direct RPC calls to each of 8+ feeds.
Detail #
MapleGlobals getLatestPrice() does not check price_ against minAnswer/maxAnswer bounds — it only checks price_ > 0. For ETH/USD and BTC/USD, Chainlink feeds have historically had non-trivial minAnswer values that could mask severe crashes. Without direct RPC inspection of all feed configurations, this cannot be fully verified. Yellow due to known pattern applicability and inability to verify all bounds within assessment scope.
Sources #
- GitHub
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 →