Breakage analysis per dependency
Midas's assessment for RD-F-052 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Breakage analysis: (1) Oracle admin key loss/compromise → silent stale prices, mint/redeem at wrong NAV (no staleness check in CustomAggregatorFeed). (2) Chainlink IB01/USD halt > 3 days → DataFeed.sol reverts, blocking vault operations. (3) USDC depeg/Circle pause → deposit/redemption halt. (4) Custodian failure (Maerki Baumann) → off-chain backing inaccessible; on-chain contracts intact but mTokens unbacked. (5) LayerZero OFT DVN compromise → unbacked mToken mint on destination chains (DVN config unknown — see F179). (6) Axelar validator compromise → forged cross-chain messages enabling unbacked mints.
Sources #
- Docs00-profile.md §700-profile.md §7 — custodial dependencies and cross-chain bridge surfaceretrieved 2026-05-16
- Sherlock 2024-08 Audit Reposherlock-audit/2024-08-midas-minter-redeemer DepositVault.sol, ManageableVault.sol — oracle call paths and failure modesretrieved 2026-05-16
Methodology #
Produce a short per-dependency text describing which protocol functions halt or degrade and impact severity if each declared dependency fails.
See the full factor methodology and distribution across all protocols →