Role separation: upgrade ≠ fee ≠ oracle

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

Evidence summary #

ACM (AccessControlManager 0x4788629abc6cfca10f9f969efdeaa1cf70c23555) grants per-function role hashes (keccak256(contractAddress, functionSig)). Upgrade, fee collection, and oracle config roles are distinct function selectors on distinct contracts — enforced through the ACM architecture by design. DEFAULT_ADMIN_ROLE assigned to deployer at construction, last tx ~300 days ago (likely renounced or transferred).

Sources #

Etherscan
AccessControlManager BscScan — verified, Solidity 0.8.130x4788629abc6cfca10f9f969efdeaa1cf70c23555retrieved 2026-04-28
GitHub
ACM source — per-function role hash architectureAccessControlManager.solretrieved 2026-04-28

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 venus factor RD-F-035 score green collected_at 2026-04-28 18:30:49