Timelock duration on upgrades
Superstate'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 contract exists for USTB or USCC proxy upgrades. All 4 USTB upgrades (Dec 2024, Feb 2025, Apr 2025, Jul 2025) and 4 USCC upgrades were executed directly by the owning EOA through the ProxyAdmin in a single transaction with zero delay between decision and execution. Data-cache governance.timelock_address = null. No TimelockController or equivalent contract found in superstateinc/ustb GitHub repo. Timelock duration = 0 hours.
Sources #
- EtherscanUSTB Proxy Upgraded Events HistoryUSTB upgrades at blocks 21340398 (Dec 2024), 21932686 (Feb 2025), 22340779 (Apr 2025), 22933833 (Jul 2025) - all single-tx direct upgrades with zero timelockretrieved 2026-05-16
- Superstate USTB GitHub Repository - No Timelocksuperstateinc/ustb repo contains no TimelockController or timelock contractretrieved 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 →