Timelock on sensitive actions

SUNSwap (sun.io)'s assessment for RD-F-033 — 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 sensitive action: setOwner (V3 factory), pausePoolManager/unpausePoolManager/setProtocolFeeController (V4 CLPoolManagerOwner), collectProtocolFee/setProtocolFee/setProtocolFeeSplitRatio (V4 ProtocolFeeController) — all execute immediately without queuing delay. V1/V2/V3 immutable factories have no sensitive admin actions beyond setOwner which is also untimed.

Sources #

GitHub
SUNSwap V4 admin contracts — no timelock on any sensitive actionsunswap-v4-core CLPoolManagerOwner.sol: pause/unpause executes immediately; ProtocolFeeController.sol: no timelock presentretrieved 2026-05-17
Internal
SUNSwap data cache — no timelock00-data-cache.json governance.timelock_address: nullretrieved 2026-05-17

Methodology #

For each sensitive action category (mint / pause / rescue / setOracle / upgrade), determine whether execution requires going through the declared timelock.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol sunswap factor RD-F-033 score red collected_at 2026-05-17 14:37:31