Chainlink aggregator min/max bound misconfig
Jupiter'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 #
Gray — cannot verify without on-chain RPC reads. Chainlink on Solana via Data Streams (Perps) and Chainlink Data Feeds (Lend) do not necessarily expose the same minAnswer/maxAnswer circuit-breaker bounds as EVM Chainlink AggregatorV3 contracts. Chainlink Data Streams are low-latency push feeds with a different architecture than AggregatorV3. Cannot verify min/max bound configuration from public documentation or WebFetch without direct Solana RPC calls. Data cache does not contain this information.
Sources #
- Curator noteOracles — Jupiter Lend Developer DocsChainlink Data Streams on Solana architecture differs from AggregatorV3; min/max bounds not verifiable from public docs without RPC accessretrieved 2026-04-29
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 →