Hyperliquid to Increase Validators Amid Transparency and Security Discussions

• Hyperliquid plans to raise its active validator set from 24 to 27 in about one month.
• Validators must self-delegate 10,000 HYPE, locked by the protocol for one year.
• Vadim noted that Hyperliquid’s public node repository distributes a signed binary rather than source code.

Hyperliquid plans to increase its active validator set from 24 to 27 in about one month, adding more operators to a network known for high-speed trading and tight system integration. DEGEN NEWS shared the update, while Hyperliquid’s announcement said validation will remain permissionless.

The expansion comes as developers and market observers examine how Hyperliquid’s validator model works. Research shared by Vadim noted that the network’s public node repository does not expose full node source code but instead provides a Dockerfile that downloads a GPG-signed binary.

Validator Set to Expand

Hyperliquid said its active validator set will rise from 24 to 27 validators in roughly one month. The network also told validators to understand the technology and testnet process before moving toward mainnet participation.

Registration remains permissionless, meaning anyone can prepare a validator. However, only the top validators by stake join the active set, which gives capital size an important role in who helps secure the network.

Validators must self-delegate 10,000 HYPE tokens. The protocol locks that stake for one year, even if the validator does not enter the active set.

That requirement adds a long-term commitment for operators. It also raises the cost of casual participation, since validators must accept the lockup before knowing whether they will secure a seat.

Closed Binary Design Draws Attention

Vadim said Hyperliquid’s public node repository does not contain full node source code but instead provides a Dockerfile that downloads a GPG-signed binary known as hl-visor.

That design differs from networks that publish full validator source code. Community reverse engineering exists, according to the same research, though the official node software remains distributed as a closed binary.

Vadim also noted that the same validators run both major layers of Hyperliquid. Those nodes sign blocks and match perpetual futures trades, linking consensus and trading execution inside one architecture.

This design supports speed. Hyperliquid uses HyperBFT, described as a HotStuff-inspired consensus system, to secure HyperCore, its perpetual order book, and HyperEVM, its smart contract layer. The system targets about a 0.07-second block time and sub-second finality.

Architecture Fuels Security Debate 

Hyperliquid’s architecture gives the network its main advantage, but it also shapes the security debate. In-memory matching, clustered validators, and one consensus system help reduce latency, especially for active trading.

However, Vadim pointed to several trade-offs. He said HyperBFT does not have a published paper with formal security proofs, while the HLP house liquidity vault uses closed-source strategies.

Moreover, the network uses jailing rather than slashing. Validators can be excluded for misbehavior, but they do not lose stake through a slashing mechanism.

Latency also matters. Documentation reportedly recommends running nodes in Tokyo to meet a sub-200 millisecond latency target, with many seed peers located in Japan.

These details explain why the validator expansion matters. Adding three active validators may improve participation, but the broader discussion now centers on transparency, validator concentration, and how Hyperliquid balances speed with decentralization as HYPE activity grows.

Related: CME, ICE Seek US Review of Hyperliquid Over Oil Market Risks