Timelock duration on upgrades

Marinade Finance'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 exists on the upgrade path. Coral Multisig (custom_onchain, analogous to Squads v3) has no timelock field. Realms MNDE DAO has 3-day voting period but no documented instruction hold-up time for the main liquid staking program. The liquid staking program is not yet under Realms control (still Coral 6/13). Zero-delay execution after 6/13 threshold met.

Sources #

Internal
SOLANA_GOVERNANCE.md — timelock absence for non-Squads-v4 programsSOLANA_GOVERNANCE.md — Squads v3 analogue: no timelock field exists in custom on-chain multisigs of this generationretrieved 2026-05-16
URL
Scroll 4: Realms-based DAOsmadscrolls substack — Realms MNDE DAO: 3-day voting period, no cool-off documentedretrieved 2026-05-16
Docs
MNDE Governance | Marinade DocumentationMarinade governance docs — no timelock parameter listedretrieved 2026-05-16

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 marinade factor RD-F-032 score red collected_at 2026-05-16 08:48:35