★ Immutable oracle address
USDD (Decentralized USD)'s assessment for RD-F-180 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
[★ F180 CRITICAL-CANDIDATE — PD-017 flag] Cannot confirm on-chain. The Median contract architecture implies oracle sources are a whitelisted set configurable by admin ('maintains a whitelist of price feed contracts which are authorized to post price updates'), suggesting oracle addresses ARE replaceable via whitelist admin function. However: (a) TRON substrate blocks on-chain contract read to verify whether TrxOracleValue oracle source address is immutable/hardcoded; (b) admin control of whitelist not confirmed; (c) Tronscan returns 403. Directional lean: likely NOT red (Median whitelist architecture is admin-configurable by design — consistent with the MakerDAO-derived pattern it implements). However formal on-chain confirmation is blocked by TRON access. Orchestrator: track F180 for T-14 post-launch promotion decision if TRON-side source becomes accessible.
Sources #
- InternalUSDD Data Cache Coverage FlagsData cache: non_evm_explorer_blocked=true; Tronscan HTML 403 — on-chain immutability verification of TrxOracleValue oracle address not obtainableretrieved 2026-05-17
- USDD Median Contract DocsMedian contract: 'maintains a whitelist of price feed contracts which are authorized to post price updates' — implies admin-configurable oracle whitelist, not immutableretrieved 2026-05-17
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 →