Role separation: upgrade ≠ fee ≠ oracle
Meteora'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 #
DBC and DAMM v2 show some role separation: feeClaimer field (fee collection) is separate from upgrade authority. pool_creator_authority controls pool creation separately from fee admin. DLMM has no oracle role (no external oracle used). However, the top-level Squads v3 multisig likely controls all admin roles including fee and config — full role separation not confirmed. Role graph incomplete without signer-level enumeration.
Sources #
- GitHubDAMM v2 GitHub — Role SeparationMeteoraAg/damm-v2 README — pool_creator_authority, feeClaimer separate role fieldsretrieved 2026-05-16
- DBC GitHub — Fee Claimer RoleMeteoraAg/dynamic-bonding-curve — owner parameter for fee claimer, separate from adminretrieved 2026-05-16
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 →