Role separation: upgrade ≠ fee ≠ oracle

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

Bridge2 roles structurally separated: proxy admin (upgrades) vs lockers (pause) vs finalizers (withdrawal execution) vs cold validators (parameter changes). Fee collection and oracle configuration are L1-side, controlled by Hyperliquid Labs via closed-source binary — not visible or separable at EVM layer.

Sources #

Docs
Hyperliquid Labs controls L1 operational parametersHyperliquid profile §6retrieved 2026-04-28
GitHub
Bridge2.sol constructor — hot/cold validator parametersBridge2.sol sourceretrieved 2026-04-28

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 hyperliquid factor RD-F-035 score yellow collected_at 2026-04-28 13:58:49