Chainlink aggregator min/max bound misconfig
Jupiter Perpetual Exchange'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 #
EVM-style Chainlink AggregatorV3Interface minAnswer/maxAnswer bounds are not present on Solana Chainlink feeds. Solana Chainlink uses a different price feed architecture without the EVM aggregator min/max circuit-breaker pattern. Additionally, Chainlink is a fallback oracle here, not the primary. The EVM-specific Chainlink min/max misconfig pattern (F060) is structurally not applicable on Solana substrate.
Sources #
- DocsJupiter Perps BPF Program — SolscanProfile §3 — Solana deployment; Solana Chainlink feeds use different architecture than EVM AggregatorV3Interface with minAnswer/maxAnswer boundsretrieved 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 →