Chainlink aggregator min/max bound misconfig

Orca'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 #

Orca does not use any Chainlink feed. Non-EVM substrate (Solana/Rust); Chainlink does not operate on Solana in the same feed-registry model as EVM. No Chainlink integration present or architecturally applicable. Factor is EVM-specific (Chainlink aggregator minAnswer/maxAnswer bounds). gap_reason: not_applicable (non-EVM substrate + no Chainlink usage).

Sources #

GitHub
Whirlpool program Cargo.toml — no oracle-provider crateorca-so/whirlpools — programs/whirlpool/Cargo.tomlretrieved 2026-05-16
Internal
Coverage flag: non_evm_substrate — Chainlink aggregator factor EVM-specific00-data-cache.json coverage_flags.non_evm_substrate = trueretrieved 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 orca factor RD-F-060 score not_applicable collected_at 2026-05-16 02:39:16