Timelock duration on upgrades
JustLend DAO's assessment for RD-F-032 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
48-hour (172,800 second) Timelock delay confirmed. setDelay() callable only by address(this) — requires queued governance transaction to change. Governance docs and profile both confirm 48h delay. Well above minimum acceptable threshold.
Sources #
- GitHubJustLend Timelock.sol — GitHub sourceTimelock.sol: setDelay() requires msg.sender == address(this) — only callable through queued governance transaction. Constructor sets initial delay.retrieved 2026-05-17
- JustLend DAO JIPs — Governance ParametersJustLend JIPs governance docs: 'the proposal will enter a lock-up period of 48 hours, after which the proposal will take effect immediately after execution.'retrieved 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 justlend factor RD-F-032 score green collected_at 2026-05-17 10:25:32