UUPS _authorizeUpgrade correctly permissioned
Liquid Collective (LsETH)'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 #
Protocol uses Transparent Upgradeable Proxy (TUPProxy) pattern, not UUPS. The _authorizeUpgrade function is only relevant for UUPS proxies. Upgrade authority routes through the ProxyAdmin Safe (0x8EE3fC0Bcd7B57429203751C5bE5fdf1AB8409f3). UUPS factor not applicable.
Sources #
- GitHubTUPProxy.sol — Liquid CollectiveTUPProxy.sol extends OZ TransparentUpgradeableProxy — not UUPSretrieved 2026-05-17
- Etherscan — River LsETH ProxyRiver proxy EIP-1967 Transparent pattern confirmed on Etherscanretrieved 2026-05-17
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 liquid-collective factor RD-F-021 score not_applicable collected_at 2026-05-16 19:46:23