Timelock on sensitive actions

Across Protocol's assessment for RD-F-033 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Timelock on sensitive actions | Specific check per action: `mint()` (ACX token) — no timelock, immediate via ACX owner Safe. `setPaused()` (HubPool) — no timelock, immediate via Council Safe. `haircutReserves()` (HubPool) — no timelock, immediate. `upgradeTo()` (SpokePools via relaySpokePoolAdminFunction) — no timelock, immediate via Council Safe. `updateTokenConfig()`/`updateGlobalConfig()` (ConfigStore) — no timelock. Only Snapshot governance proposals have the 5-day oSnap liveness, and con...

Sources #

Curator note
Extracted from 02-governance-admin.md — RD-F-033; no URL citedretrieved 2026-04-28

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 across-protocol factor RD-F-033 score gray collected_at 2026-04-30 21:19:18