Timelock on sensitive actions
Morpho V1 (Morpho Blue + MetaMorpho)'s assessment for RD-F-033 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Morpho Blue admin functions (setFee, setFeeRecipient, enableIrm, enableLltv, setOwner) route through 24h Zodiac Delay Modifier. No pause/rescue functions exist. Oracle is market-level (not DAO-controlled). 3-of-5 actions timelocked; no upgrade path needed (immutable core).
Sources #
- Etherscanhttps://etherscan.io/address/0x68d11129a514c45716e55b9771813f117c4c2fa5retrieved 2026-04-27
- https://github.com/morpho-org/morpho-blue/blob/main/src/Morpho.solretrieved 2026-04-27
Methodology #
For each sensitive action category (mint / pause / rescue / setOracle / upgrade), determine whether execution requires going through the declared timelock.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol morpho-v1 factor RD-F-033 score yellow collected_at 2026-04-30 21:19:13