Timelock duration on upgrades
Liquity V1 + V2 (LUSD / BOLD)'s assessment for RD-F-032 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No timelock is correct-by-design for an immutable protocol. No upgrade operations exist that require timelock gating. v2 Governance has no timelock for incentive-direction decisions (low-stakes: redirects 25% of revenue to initiatives, cannot drain collateral). Timelock absence is not a red here — it is architecturally consistent with the immutable design.
Sources #
- InternalLiquity Protocol Profile §6.research/protocols/liquity/00-profile.md §6 — timelock_address: null by designretrieved 2026-05-16
- Liquity v2 FAQ — GeneralLiquity v2 docs: governance limited to PIL incentive direction; cannot modify core contractsretrieved 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 liquity factor RD-F-032 score not_applicable collected_at 2026-05-16 10:35:50