Timelock duration on upgrades
Multipli's assessment for RD-F-032 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No on-chain timelock contract found on any chain. Docs claim 24-hour delay for rwaUSD parameter changes but no TimelockController address is published or deployed as of 2026-05-17. MultipliVault UUPS upgrades gated by requiresAuth only (no TimelockController intermediary). Deployment script Base.s.sol deploys no timelock.
Sources #
- Internal00-data-cache.json governance.timelock_address=nullcache governance.timelock_address=nullretrieved 2026-05-17
- Multipli Base.s.sol — no timelock deployedBase.s.sol deployment script: no TimelockController deployment stepretrieved 2026-05-17
- Multipli governance docs — claims 24h delay but no on-chain timelock address publisheddocs.multipli.fi governance: 'minimum delay on parameter changes (24 hours)' — no contract address givenretrieved 2026-05-17
Methodology #
Read the timelock delay (in hours) between a queued upgrade proposal and its executable state.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol multipli factor RD-F-032 score red collected_at 2026-05-17 11:48:35