Role separation: upgrade ≠ fee ≠ oracle
Balancer (v2 + v3)'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 #
Upgrade/configuration: DAO Multisig (6-of-11) via Authorizer. Fee collection: ProtocolFeesCollector (0xce886865...) — separate contract. Treasury: Treasury Multisig (5-of-7, 0x0EFcCBb9...). Oracle/rate-provider config: pool-level, not a single protocol role. OpCo Safe (3-of-4) for operational spending. Some concentration at the DAO Multisig level across configuration types. Not full role separation across all three dimensions.
Sources #
- EtherscanBalancer V2: Protocol Fees CollectorProtocol Fees Collector 0xce88686553686DA562CE7Cea497CE749DA109f9Fretrieved 2026-05-05
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 →