Timelock on sensitive actions
Marinade Finance's assessment for RD-F-033 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No action category (mint/pause/rescue/upgrade) routes through a timelock. pause() and emergency_unstake() callable immediately by 4/7 Council; upgrades executable immediately after 6/13 consensus. No TimelockController equivalent exists in Solana for this protocol.
Sources #
- GitHubMarinade lib.rs — admin instruction listmarinade-finance/liquid-staking-program/lib.rs — pause, resume, emergency_unstake, change_authority functions (no timelock in any)retrieved 2026-05-16
- MNDE Governance | Marinade DocumentationMarinade governance docs — no timelock for any action category documentedretrieved 2026-05-16
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 marinade factor RD-F-033 score red collected_at 2026-05-16 08:48:35