Timelock on sensitive actions

Lista DAO's assessment for RD-F-033 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Timelock gates lending cluster operations (upgrades go through it). CDP Interaction.sol admin functions (rely/deny, removeCollateralType, parameter changes) use wards-based direct access WITHOUT routing through the Timelock. setSupplyCap on lisUSD is not timelocked. Partial coverage: 2-3 of 5 action types timelocked.

Sources #

GitHub
Lista DAO Interaction.sol — admin functions without timelockInteraction.sol: auth modifier uses wards[msg.sender]; no TimelockController guard in admin functionsretrieved 2026-05-12
GitHub
Lista DAO hay.sol setSupplyCap — no timelockhay.sol: setSupplyCap(uint256 wad) public auth — no timelock guardretrieved 2026-05-12

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 lista-dao factor RD-F-033 score yellow collected_at 2026-05-12 17:54:05