Oracle price deviation >X% from secondary

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

Evidence summary #

Oracle price deviation signal. T-09 phase-2. Applicable: Midas DataFeed publishes daily NAV attestations per mToken; secondary cross-check against RWA.xyz or DeFiLlama RWA prices is feasible but not configured. NAV is issuer-attested at daily cadence, not per-block AMM spot price; this changes the deviation signal's character (daily staleness vs per-block manipulation). No secondary oracle reference feed mapped in pipeline. Production pipeline not implemented; per-asset secondary-source map and per-protocol oracle-usage map are prerequisites per T-09 §3.2 gating work.

Sources #

Docs
Sherlock 2024-08 midas-minter-redeemer audit scope — DataFeedMidas DataFeed described in Sherlock 2024-08 audit scope — custom price feed aggregators providing daily NAV attestations for mToken pricingretrieved 2026-05-16

Methodology #

Detect whether the primary oracle's reported price deviates >X% from the best available secondary source (another feed or venue).

See the full factor methodology and distribution across all protocols →

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