Chainlink aggregator min/max bound misconfig

Liquid Collective (LsETH)'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 #

Protocol does not use Chainlink aggregators in the conversion rate path. Pipeline-flagged Chainlink feeds (18 entries) verified as false positives from EVM storage scanning — not consumed by River.1.sol or Oracle.1.sol. No AggregatorV3Interface call found in core contracts.

Sources #

GitHub
Liquid Collective River.1.sol sourceRiver.1.sol and Oracle.1.sol — no AggregatorV3Interface, no latestAnswer(), no latestRoundData()retrieved 2026-05-17
Internal
00-data-cache.json and 00-profile.md §7data cache oracle_feeds — 18 Chainlink entries; profile §7 flags these as likely false positives needing verification; confirmed not consumed by core contractsretrieved 2026-05-17

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 liquid-collective factor RD-F-060 score not_applicable collected_at 2026-05-16 19:46:23