Timelock on sensitive actions
Raydium'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 #
24h timelock applies to program upgrades. Admin fee collection functions (WithdrawPnl in AMM V4, collect_protocol_fee in CLMM) require multisig signatures but do not have an independent timelock on execution. Treasury multisig gates fee withdrawals but no dedicated timelock per-action confirmed for sensitive actions beyond upgrades.
Sources #
- GitHubRaydium CLMM collect_protocol_fee — no independent timelockgithub.com/raydium-io/raydium-clmm collect_protocol_fee.rsretrieved 2026-04-29
- Raydium AMM V4 processor.rs — process_withdrawpnl signer checksgithub.com/raydium-io/raydium-amm/blob/master/program/src/processor.rsretrieved 2026-04-29
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 raydium factor RD-F-033 score yellow collected_at 2026-04-29 12:31:55