★ Immutable oracle address
Orca's assessment for RD-F-180 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
NOT_APPLICABLE — architectural basis: Orca Whirlpools uses no external oracle in the swap pricing path. RD-F-180 tests whether an oracle source address is hardcoded (EVM immutable, non-EVM hardcoded, or closed-source binary embedding) such that the protocol cannot replace the oracle if the underlying asset depegs. Because Whirlpools has no oracle address at all — pricing is derived from pool reserves (sqrt_price, tick state) — the failure mode this factor tests is structurally absent. Evaluated on merits per briefing instruction. Orchestrator flag: F180 critical-candidate status per PD-017 is noted; inapplicability here does not affect its star status for other protocols. gap_reason: not_applicable (no oracle address exists to be mutable or immutable).
Sources #
- GitHuboracle.rs is internal adaptive-fee state; no external oracle address hardcodedorca-so/whirlpools — programs/whirlpool/src/state/oracle.rs (internal adaptive-fee tracker only)retrieved 2026-05-16
- Cache and profile confirm no external oracle in swap path00-data-cache.json sources.oracle_feeds = [] and 00-profile.md §7retrieved 2026-05-16
- Cargo.toml — confirms no oracle-provider crate; no external oracle address exists to be immutableorca-so/whirlpools — programs/whirlpool/Cargo.toml (no oracle crate; no external oracle address)retrieved 2026-05-16
Methodology #
Determine whether any collateral oracle address is marked `immutable` in protocol config with no admin-replaceable adapter wrapper, preventing the protocol from repricing when the upstream asset depegs.
See the full factor methodology and distribution across all protocols →