Role separation: upgrade ≠ fee ≠ oracle

Jito'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 #

Program upgrades: Squads multisig PDA. Stake pool fee params: Squads multisig (same address). Merkle upload (tip distribution): separate key 8F4jGUmxF36vQ6yabnsxX6AQVXdKBhs8kGSUuRKSg8Xt. TipRouter NCN: programmatic post-transition. Partial role separation — upgrade and fee management may share the same Squads multisig, but merkle authority is separate. Not fully separated across all roles.

Sources #

URL
Jito MEV on Solana — Squads SpotlightSquads blog: Jito uses Squads for both stake pool manager and program upgrades (may be same multisig)retrieved 2026-04-29
Docs
Jito MEV On-Chain AddressesGitbook on-chain addresses: separate addresses for upgrade authority and merkle upload authorityretrieved 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 jito factor RD-F-035 score yellow collected_at 2026-04-29 15:50:23