Role separation: upgrade ≠ fee ≠ oracle

Fluid'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 authority = Avocado admin (0x4F6F977). Fee/revenue collection = Auths role. Guardians = pause only. Oracle config within vaults = Auth-controlled. But updateAuths() (role grants) callable by onlyGovernance which maps to same Avocado admin. Upgrade and role-management authority are the same ultimate controller.

Sources #

GitHub
AdminModule: onlyGovernance, onlyAuths, onlyGuardians — no timelock wrapper on any functionfluid-contracts-public/contracts/liquidity/adminModule/main.solretrieved 2026-04-29

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 fluid factor RD-F-035 score yellow collected_at 2026-04-29 10:35:01