Chainlink aggregator min/max bound misconfig
PancakeSwap'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 #
BSC Chainlink feed proxies confirmed as EACAggregatorProxy (standard Chainlink). Min/max bounds set in underlying aggregator (not the proxy). Bounds require direct aggregator state read. Note: some feed proxy addresses show creation ~103 days ago (approximately January 2026), which may indicate recently updated proxy addresses — normal for Chainlink but worth verifying these are canonical production addresses.
Sources #
- EtherscanChainlink ETH/USD BSC — EACAggregatorProxyBscScan 0x06159da512fBF70cb5562E79C28955cA159F0e3D — EACAggregatorProxy, created ~103 days ago by 0xfb166090...d3A19b01Cretrieved 2026-04-28
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 →