UUPS _authorizeUpgrade correctly permissioned

Liquity V1 + V2 (LUSD / BOLD)'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 #

Neither v1 nor v2 use the UUPS proxy upgrade pattern. All contracts are direct non-upgradeable implementations with constructor-based initialization. _authorizeUpgrade does not exist in any Liquity contract.

Sources #

GitHub
Liquity v2 BorrowerOperations.sol sourcev2 BorrowerOperations — constructor-based, no proxy, no _authorizeUpgraderetrieved 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 liquity factor RD-F-021 score not_applicable collected_at 2026-05-16 10:35:50