★ Immutable oracle address
Symbiotic'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 #
[★ CANDIDATE PD-017 — NOT_APPLICABLE] No oracle address variable exists in any Symbiotic core contract, whether declared immutable or otherwise. The replaceability question is structurally moot: there is no oracle address to replace. Verified across Vault.sol, DefaultCollateral.sol, VetoSlasher.sol, BaseSlasher.sol — all confirmed oracle-address-free. Consumer networks that embed their own immutable oracle addresses face this risk independently; Symbiotic primitive does not. PD-017 note: factor evaluated as instructed per orchestrator scope; not_applicable is the correct disposition.
Sources #
- InternalSymbiotic protocol profile meta.json — F180 verification00-profile.meta.json: oracle_used_by_core = false; oracle_flag_note confirms no oracle address in coreretrieved 2026-05-16
- Symbiotic VetoSlasher.sol — F180 immutable oracle absence verificationVetoSlasher.sol — no immutable oracle address variable; veto logic based on stake units onlyretrieved 2026-05-16
- DefaultCollateral wstETH — F180 verificationDefaultCollateral wstETH Etherscan — no immutable oracle address in state variablesretrieved 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 →