Timelock duration on upgrades

GMX v2 (GMX Synthetics)'s assessment for RD-F-032 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

All five timelocks (3 Arbitrum + 2 Avalanche) have minDelay=86400 seconds (24 hours). The operational Timelock enforces MAX_TIMELOCK_DELAY=5 days. 24-hour delay is functional but below the 48h+ tier-1 norm for a $243M TVL protocol.

Sources #

GitHub
ConfigTimelockController — 86400sConfigTimelockController.json minDelay=86400retrieved 2026-05-05
GitHub
Arbitrum Timelock — 86400s minDelayTimelock.json minDelay=86400; MAX_TIMELOCK_DELAY=5 days in constructor argsretrieved 2026-05-05
GitHub
GovTimelockController — 86400sGovTimelockController.json minDelay=86400retrieved 2026-05-05

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 gmx-v2 factor RD-F-032 score yellow collected_at 2026-05-05 11:15:06