defirisk.co
rubric v1.7.0

Immutable oracle address

M^0's assessment for RD-F-180 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

CRITICAL-CANDIDATE per T-12 PD-017 — flagged for orchestrator T-14 tracking. EarnerRateModel and MinterRateModel addresses are NOT hardcoded as immutable in MinterGateway; they are read dynamically from the TTG Registrar via TTGRegistrarReader.getMinterRateModel() and getEarnerRateModel(). The TTG Registrar is governance-writable via TTG proposals, so rate models are replaceable without a full protocol upgrade. YELLOW (not RED) because replacement mechanism exists and is enforced on-chain. Residual concern: TTG 15-day epoch cycle means up to 15+ days before a broken rate model can be replaced. The M^0 rate model replacement path is materially different from the immutable oracle address pattern (USR/USDX/xUSD/USD0++) that drove F180 star promotion — may warrant GREEN reassessment at T-14.

Sources #

  • GitHub
    MinterGateway.sol sourcem0-foundation/protocol main/src/MinterGateway.sol — ttgRegistrar immutable but rateModel read from Registrar at call time via TTGRegistrarReaderretrieved 2026-05-16
  • Docs
    M^0 TTG Governance Overviewdocs.m0.org/home/technical-documentations/ttg-governance/overview/ — TTG 15-day epoch cycle governs rate model replacementretrieved 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 →

rubric_version v1.7.0 protocol m0 factor RD-F-180 score yellow collected_at 2026-05-16 09:46:19