Bridge signer-set change proposed/executed
Hyperliquid's assessment for RD-F-103 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
April 22, 2025: Hyperliquid expanded validator set from ~4 (Hyperliquid Labs-controlled) to 21 permissionless nodes. The hotValidatorSetHash in Bridge2 would have been updated as the active validator set changed. The Hyper Foundation announced the change via X post (@HyperFND) on April 22, 2025 — however, no formal on-chain governance proposal with a 24-hour machine-readable change-management pre-announcement was identified, which is the suppression condition under the RD-F-103 detection rule. Under strict T-09 RD-F-103 rules, this would have fired on April 22 as an unscheduled bridge signer-set change. Lockers set remains: 5 addresses, 2-of-5 threshold. At assessment date (April 28, 2026) this event is 6 days old and partially clearing. Current posture is improved (21 permissionless validators vs. prior 4-validator centralization) but the transition itself was a signal event.
Sources #
- URL
- https://x.com/HyperFND/status/1914520069897670826retrieved 2026-04-28
Methodology #
Detect whether a bridge validator or signer-set change has been proposed or executed.
See the full factor methodology and distribution across all protocols →