Timelock duration on upgrades

Dolomite'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 #

1-day (86,400s) stated at launch per docs. Falls at yellow boundary (24h exactly; green requires >=48h). Docs state intent to increase incrementally. Current on-chain value not directly confirmed (Arbiscan returned 403 for readContract).

Sources #

Partner feed
Data cache — timelock delay not readdata-cache governance.timelock_delay_seconds=null (pipeline did not read on-chain value)retrieved 2026-05-16
Docs
Dolomite Admin Privileges — secondsTimeLockeddocs.dolomite.io/admin-privileges: at launch delay is 1 day (86,400 seconds)retrieved 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 dolomite factor RD-F-032 score yellow collected_at 2026-05-16 11:12:56