Timelock duration on upgrades
Liquid Collective (LsETH)'s assessment for RD-F-032 — scored red on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
0 hours timelock. No Timelock contract identified anywhere in the governance stack. Data cache confirms governance.timelock_address: null and timelock_delay_seconds: null. Proxy Admin Safe executes upgrades immediately upon 4-of-7 signature collection. Governor Safe executes protocol parameter changes immediately upon 4-of-7 signatures. No queue, no delay, no guardian veto window.
Sources #
- InternalData cache — confirmed no timelock contract.research/protocols/liquid-collective/00-data-cache.json §sources.governance.timelock_address=null, timelock_delay_seconds=nullretrieved 2026-05-16
- Liquid Collective Architecture — no timelock described in upgrade pathdocs.liquidcollective.io/eth/overview/architecture — no timelock describedretrieved 2026-05-17
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 liquid-collective factor RD-F-032 score red collected_at 2026-05-16 19:46:23