Chainlink aggregator min/max bound misconfig

BENQI's assessment for RD-F-060 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Chainlink V3 aggregator proxies on Avalanche do not consistently expose `minAnswer`/`maxAnswer` circuit-breaker bounds via public functions. The V3 aggregator model deprecated these bounds in many feeds. No specific misconfig evidence found for BENQI's Chainlink feeds. Cannot assess without direct on-chain read of each feed's aggregator proxy.

Sources #

URL
Chainlink Data Feeds DocumentationChainlink data feeds documentation — V3 aggregator architectureretrieved 2026-05-16
Internal
Cache oracle_feeds — Chainlink feed addressesrisk-dashboard/.research/protocols/benqi/00-data-cache.json §sources.oracle_feeds — feed addresses listedretrieved 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 →

rubric_version v1.7.0 protocol benqi factor RD-F-060 score gray collected_at 2026-05-16 11:02:12