UUPS _authorizeUpgrade correctly permissioned

Jupiter Perpetual Exchange's assessment for RD-F-021 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

UUPS proxy pattern is EVM-specific. Solana uses BPFLoaderUpgradeable for program upgrades — there is no proxy contract, no _authorizeUpgrade function, and no EIP-1967 proxy pattern. Structurally not_applicable.

Sources #

Docs
Solscan — Jupiter Perps BPF programProfile §3: 'BPFLoaderUpgradeable is the upgrade mechanism; upgrades are executed by whoever holds the upgrade_authority in the ProgramData account' — no EVM proxy patternretrieved 2026-05-16

Methodology #

Determine whether the UUPS implementation defines `_authorizeUpgrade(address)` restricted to owner/admin/timelock (not open to arbitrary callers).

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol jupiter-perps factor RD-F-021 score not_applicable collected_at 2026-05-16 01:53:11