Timelock duration on upgrades

SUNSwap (sun.io)'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 on any upgrade or admin operation. V3 factory setOwner() executes immediately. V4 CLPoolManagerOwner pause/unpause/setProtocolFeeController execute immediately. ProtocolFeeController all admin functions execute immediately. Data cache confirms timelock_address: null. SUN DAO weekly Thursday snapshot provides parameter cadence (~7d) for gauge weights only — not a timelock on admin operations.

Sources #

GitHub
SUNSwap V4 ProtocolFeeController — no timelocksunswap-v4-core ProtocolFeeController.sol: no timelock present, admin functions execute immediatelyretrieved 2026-05-17
Internal
SUNSwap data cache — no timelock00-data-cache.json governance.timelock_address: null, timelock_delay_seconds: nullretrieved 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 sunswap factor RD-F-032 score red collected_at 2026-05-17 14:37:31