Role separation: upgrade ≠ fee ≠ oracle

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

Evidence summary #

Role separation: upgrade ≠ fee ≠ oracle | All roles (upgrade, fee via setProtocolFeeCapture, oracle config via setIdentifier, bond config via setBond) converge on the single Council multisig as HubPool owner. ConfigStore owner (presume also Council Safe) controls fee and parameter updates. No role separation. | HubPool ABI; ConfigStore ABI (Ownable, single owner); governance manual | yellow

Sources #

Curator note
Extracted from 02-governance-admin.md — RD-F-035; no URL citedretrieved 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 across-protocol factor RD-F-035 score gray collected_at 2026-04-30 21:19:18