Oracle role per asset

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

Evidence summary #

mTBILL NAV: MTBillCustomAggregatorFeed (primary, sole — no secondary or fallback). mBASIS NAV: MBasisCustomAggregatorFeed (primary, sole). Payment tokens (USDC, WBTC): per-token DataFeed.sol wrapped Chainlink feed (primary, sole per tokensConfig mapping in DepositVault). No secondary or fallback oracle identified for any asset. Single-oracle-per-asset design increases operational risk on oracle admin failure or Chainlink IB01/USD halt.

Sources #

GitHub
DepositVault.sol — Sherlock 2024-08sherlock-audit/2024-08-midas-minter-redeemer DepositVault.sol: mTokenDataFeed.getDataInBase18() sole oracle call; tokensConfig mapping per-token DataFeedretrieved 2026-05-16
Docs
00-profile.md §7 Oracle descriptionProfile §7: oracle_feeds in cache is advisory; actual Midas DataFeed architecture per Sherlock audit reposretrieved 2026-05-16

Methodology #

For each oracle, classify its role as Primary / Secondary / Fallback per asset/market.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol midas factor RD-F-049 score yellow collected_at 2026-05-16 09:34:55