Oracle providers used
Midas's assessment for RD-F-048 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Midas uses a proprietary issuer-push oracle (MTBillCustomAggregatorFeed at proxy 0x056339C044055819E8Db84E71f5f2E1F536b2E5b, impl 0x0d84eC93e9a734184c7f59f61342f432444efc1b) for mToken NAV pricing. The CustomAggregatorV3CompatibleFeed implements Chainlink's AggregatorV3 interface but receives prices via admin-push (setRoundData), not from an external feed. DataFeed.sol (Sherlock 2024-05 scope) wraps Chainlink IB01/USD aggregator (0x32d1463EB53b73C095625719Afa544D5426354cB, 16 oracle nodes, 2% deviation threshold) for the underlying T-bill reference price. Pipeline cache's 18 Chainlink feeds are advisory false-positives and do not reflect Midas's actual oracle architecture.
Sources #
- GitHubSherlock 2024-08 Midas Minter/Redeemer Audit Reposherlock-audit/2024-08-midas-minter-redeemer CustomAggregatorV3CompatibleFeed.sol and MTBillCustomAggregatorFeed.solretrieved 2026-05-16
- MTBillCustomAggregatorFeed Proxy — EtherscanMTBillCustomAggregatorFeed proxy 0x056339C044055819E8Db84E71f5f2E1F536b2E5b — 244 transactions, Set Round Data pattern confirms issuer-push oracleretrieved 2026-05-16
- Chainlink IB01/USD Price FeedChainlink IB01/USD feed — 0x32d1463EB53b73C095625719Afa544D5426354cB, 16 oracle operators, 2% deviation, Ethereum Mainnetretrieved 2026-05-16
Methodology #
List all oracle providers used (Chainlink, Pyth, Redstone, Uniswap-TWAP, in-house, etc.) per asset/market pair in the protocol.
See the full factor methodology and distribution across all protocols →