Role separation: upgrade ≠ fee ≠ oracle
ether.fi'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 #
RoleRegistry implements RBAC with fine-grained role separation: PROTOCOL_UPGRADER, LIQUIDITY_POOL_ADMIN_ROLE (fee recipient), ETHERFI_ORACLE_EXECUTOR_ADMIN_ROLE (oracle config), and dozens of contract-specific roles. These are distinct and assignable to different addresses.
Sources #
- GitHubRoleRegistry — PROTOCOL_PAUSER, PROTOCOL_UNPAUSER defined; other roles in consuming contractsRoleRegistry.sol — RBAC role definitionsretrieved 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 ether-fi factor RD-F-035 score green collected_at 2026-04-28 13:58:46