Dependency graph (protocols depended upon)
Midas's assessment for RD-F-050 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
External dependencies: (1) Midas oracle admin key (M_TBILL_CUSTOM_AGGREGATOR_FEED_ADMIN_ROLE, approx 0xEc581705...50BF64792) for continuous NAV price updates; (2) Chainlink IB01/USD aggregator for underlying T-bill price; (3) USDC/Circle for payment token; (4) off-chain custodians: Maerki Baumann & Co. AG (Switzerland) and Fordefi/Fortuna Custody; (5) BlackRock Treasury Bond fund (mTBILL underlying); (6) LayerZero OFT infrastructure (DVNs, executor) for cross-chain delivery; (7) Axelar ITS for additional cross-chain routes. Multi-layer dependency cascade: off-chain custodian failure → NAV attestation breaks → mToken backing compromised even if smart contracts intact.
Sources #
- Docs00-profile.md §700-profile.md §7 — external dependencies enumerated including custodians, USDC, LayerZero OFT, Axelar vaultretrieved 2026-05-16
- Midas Bug Bounty Programme — LinkedInLinkedIn bug-bounty announcement 2026-03-24 confirming LayerZero OFT and Axelar vault as in-scope cross-chain dependenciesretrieved 2026-05-16
Methodology #
List all external protocols whose failure would directly impair this protocol (LST providers, bridges, stablecoin issuers, keepers).
See the full factor methodology and distribution across all protocols →