Timelock duration on upgrades

Usual (USD0 / bUSD0 / USUAL)'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 #

No timelock exists. Cache: governance.timelock_address = null, timelock_delay_seconds = null. All proxy upgrades execute immediately upon multisig threshold being reached. Etherscan constructor arg analysis on USD0 and DaoCollateral proxies confirms no timelock in admin chain. Red at $104.77M TVL stablecoin.

Sources #

Internal
Usual data cache — no timelock00-data-cache.json: governance.timelock_address = null, governance.timelock_delay_seconds = nullretrieved 2026-05-17
Etherscan
USD0 proxy — no timelock in admin chainUSD0 proxy 0x73A15... and DaoCollateral proxy 0xde6e1... constructor args: initialOwner = 0xaaDa24... (Safe direct, no intermediate timelock)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 usual factor RD-F-032 score red collected_at 2026-05-16 20:39:44