Security-Council threshold reduction (RT)
Hyperliquid's assessment for RD-F-182 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Bridge2 Lockers set: 5 addresses, 2-of-5 threshold (per Bridge2 architecture documentation and Bridge2.sol). The changeLockerThreshold() function requires cold wallet quorum to execute. No documented locker threshold reduction or locker removal in the assessment period. The April 2025 validator set expansion was a signer-ADDITION (from ~4 to 21 permissionless nodes) — a positive decentralization direction — which is monitored under RD-F-103 (signer set change), not F182 (threshold reduction). No F182-type Security Council threshold reduction is documented. Current 2-of-5 locker threshold appears stable. Signal would fire if changeLockerThreshold() is called without pre-announcement.
Sources #
- GitHubhttps://github.com/hyperliquid-dex/contracts/blob/master/Bridge2.solretrieved 2026-04-28
- https://hyperliquid.gitbook.io/hyperliquid-docs/hypercore/bridgeretrieved 2026-04-28
Methodology #
Detect in real-time whether the bridge/protocol Security Council multisig executes a threshold reduction (e.g. 3/5 → 2/5), timelock removal, or new-signer addition within ≤14 days of either of those events.
See the full factor methodology and distribution across all protocols →