Hyperliquid validators and governance
Verified against Hyperliquid docs: Staking and Hyperliquid public info API · by Hyperliquid Academy
The set, live
| Measure | Value |
|---|---|
| Validators in the set | 35 |
| Active | 27 |
| Jailed | 6 |
| HYPE staked | 442,215,116 HYPE |
| Largest validator, share of active stake | 12.55% |
| Median commission | 3% |
| Median predicted APR | 2.16% |
Three of those numbers are worth reading carefully.
Active versus total. Validators can be jailed for poor performance, so the set that is actually producing blocks is smaller than the set that exists. A guide quoting only the headline count is quoting the flattering number.
The largest validator’s share. Concentration matters more than count. Twenty validators where one holds a third of the stake is less decentralised than ten where nobody holds more than fifteen percent.
Median predicted APR. This is the staking reward, and it is modest. Anyone staking HYPE for the yield is making a decision dominated by the token’s price, not by this figure. The fee discount is usually the better reason.
How delegation works
Delegated proof-of-stake, and the documentation uses stake and delegate interchangeably because there is no other kind here.
You stake HYPE to validators, any number of them, from a staking account that is separate from your spot balance.
A validator needs 10,000 HYPE of self-delegation to become active. That is the barrier to running one — meaningful, not prohibitive.
Unstaking takes seven days. Transfers from the staking account back to spot sit in a queue for that long, and an address can have at most five pending withdrawals at a time. Plan around it, or use a liquid staking token and accept the risks that adds.
There is no automatic slashing yet
The documentation reserves slashing for provably malicious behaviour such as double-signing a block at the same round, and states that it is not currently implemented.
Read that both ways. Your delegated stake is not at risk of being burned for a validator’s mistake — which is unusual and, for a delegator, good. And the economic deterrent against misbehaviour is weaker than on chains where slashing is live. Jailing for poor performance exists; slashing for malice does not, yet.
What governance actually decides
This is where Hyperliquid diverges from most “governance” that amounts to voting on a treasury grant.
In September 2025, validators voted — stake-weighted, on-chain — on who would issue the network’s native stablecoin. Established issuers bid. The winner offered less revenue sharing than several of them and won anyway.
That is a commercial decision of real consequence, made by the people securing the network rather than by an operator announcing it. What happened next is its own story, including the eventual wind-down.
Whether you like the outcome is separate from the mechanism. The mechanism did something.
The honest decentralisation assessment
A small validator set is a genuine trade-off and it is not one to hand-wave.
Why it is small. This network runs an order book with latency people actually notice. Consensus over a large, geographically scattered validator set is slower than consensus over a small one. The set size is a performance decision, and the performance is the product.
What that costs. Fewer independent parties, and a correspondingly lower bar for a colluding majority. Concentration of stake, visible in the table above, is the metric that tells you how close that bar is.
What it does not cost. Custody. Your funds are yours regardless of who validates: a validator cannot move your balance, and the settlement is on-chain and public whoever produced the block. The rest of the threat model.
The fair summary is that this is more decentralised than a centralised exchange and less than a general-purpose L1, by design, in exchange for being fast enough to run an order book. Anyone selling you either extreme is selling something.
If you want to participate
Stake, and choose deliberately. Spreading stake across smaller validators improves the concentration number; staking with the largest worsens it. The reward difference is small, so this is close to a free choice.
Check commission and uptime. A validator taking a high commission with imperfect uptime is worse on both axes, and both are public.
Remember the seven days. Staked HYPE is not liquid, and the queue does not care why you want it back.
Where to go next
Staking HYPE, including the fee discount that is usually the better reason to do it, and how HyperCore and HyperEVM fit together — the same validators secure both.
Frequently asked questions
How many validators are there?
The table on this page reads the live count from the exchange API, split into active and jailed. It is a small set by the standards of a general-purpose chain, which is the honest framing for a network optimised for order-book latency.
How are validators chosen?
By stake. It is delegated proof-of-stake, so anyone can stake HYPE to any validator, and a validator needs a self-delegation of 10,000 HYPE to become active.
Can validators censor my orders?
Consensus decides block contents, so in principle a colluding majority of stake could exclude transactions. Nothing about the design makes that impossible, which is why stake concentration is the number worth watching rather than the validator count.
Is there slashing?
Not automatically. The documentation reserves slashing for provably malicious behaviour such as double-signing, and says it is not currently implemented. Validators can be jailed for poor performance.
How long does unstaking take?
Transfers from the staking account to the spot account have a seven-day queue, and an address can have at most five pending withdrawals at once.
What do governance votes actually decide?
Real things. The USDH stablecoin issuer was chosen by a stake-weighted validator vote against bids from several established issuers, which is a commercial decision most chains make privately.
Sources
- Hyperliquid docs: Stakinghyperliquid.gitbook.io
- Hyperliquid public info APIapi.hyperliquid.xyz
We link the primary source for every number on this page. If a figure here disagrees with the Hyperliquid documentation, the documentation is right and we want to know.