Role separation: upgrade ≠ fee ≠ oracle

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

Evidence summary #

Interaction.sol uses unified wards mapping for all admin operations including oracle config, fee rates, and upgrade — roles not separated at CDP level. At Timelock level: multisig holds PROPOSER+EXECUTOR; deployer EOA holds DEFAULT_ADMIN_ROLE. Partial separation exists at Timelock layer only.

Sources #

Etherscan
Lista DAO Timelock role separation — BscScanTimelock roles: PROPOSER+EXECUTOR = multisig; DEFAULT_ADMIN = deployer EOAretrieved 2026-05-12
GitHub
Lista DAO Interaction.sol — unified admin rolesInteraction.sol: unified wards for oracle, fees, and upgrade; no AccessControl role separationretrieved 2026-05-12

Methodology #

Determine whether the upgrade role, fee-collection role, and oracle-config role are assigned to distinct addresses.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol lista-dao factor RD-F-035 score yellow collected_at 2026-05-12 17:54:05