Hyperliquid staking is validator delegation with two lockup clocks
Hyperliquid staking is delegated proof-of-stake on HyperCore: HYPE moves from the spot balance into a staking balance, then backs one or more validators. Each delegation is locked for 1 day. Undelegation returns HYPE to the staking balance immediately after that lock, but moving it back to spot starts a separate 7-day queue. Rewards accrue every minute, distribute daily, and automatically compound with the chosen validator, after its commission.
Posted 2026-08-06
Validator commission and jailed status decide whether displayed rewards reach the delegator's compounding balance.
Do not rank validators by displayed yield alone
Validator selection should start with commission, active status, self-delegation, and operating behavior. Ranking only by a displayed annual rate misses two distinct outcomes: commission removes a share, while a jailed validator produces no reward. Compare the validator record before signing, then revisit it after delegation because status changes onchain.
Each active validator must self-delegate 10,000 HYPE, locked for one year. Falling below 10,000 HYPE puts that validator into undelegate-only mode, so new delegations stop and total stake can only decline. Low commission still does not outweigh repeated jailing. A delegator may spread HYPE across any number of validators, which separates operator exposure without changing the exit rules for each allocation.
Treat the validator address as the stable identifier. Names and descriptions are operator profile fields, while delegation records store a 42-character address, the HYPE amount, and a lock-until timestamp. Recording those three fields makes later comparisons precise, especially when allocations are split.
Commission and locked liquidity form the real staking cost
Validator commission is deducted from rewards before the delegator's share is credited. It is a reward percentage, not a charge against principal. Hyperliquid restricts later increases: a commission may rise only when the new rate is 1% or lower. The 1% rule governs increases, not every validator's starting rate, so read the displayed commission itself.
Commission changes future reward flow, not HYPE already distributed. Because rewards compound automatically, the commission drag compounds too. Compare the after-commission rate with the network rate, then reserve enough spot balance for near-term actions.
The other cost is unavailable liquidity. A newly delegated amount cannot be undelegated for 1 day, and a transfer from staking to spot waits 7 days. During that exit, HYPE cannot be sold from the spot book or used elsewhere in HyperCore. Price moves and forgone uses matter even though they are not protocol fees. Hyperliquid staking therefore fits capital that does not need an immediate exit.
The one-day lock and seven-day queue are separate clocks
The delegation lock applies to each validator allocation, while the withdrawal queue applies to the address's move back to spot. During the first 1 day, the allocation stays with that validator. Once unlocked, partial or full undelegation returns HYPE to the staking balance immediately; redelegating from there avoids a spot withdrawal.
Undelegated HYPE stays usable inside the staking account. It stops backing the previous validator and no longer earns that validator's rewards, yet it can be delegated again without waiting 7 days. Validator switching is therefore faster than returning funds to spot.
Transfers from the staking account to the spot account enter a 7-day queue, and each address can hold at most 5 pending withdrawals. Each partial staking-to-spot transfer consumes one queue slot. A sixth request must wait until an earlier item completes, so frequent small withdrawals create an operational bottleneck.
Count backward from any date when spot liquidity is needed. The one-day lock matters only if delegation is still fresh; the seven-day queue starts after the staking-to-spot action, not after the original delegation. Simply undelegating does not start it.
A hypothetical 30-day reward calculation
The reward calculation starts with gross network rate, validator commission, principal, and time. Every changing input here is hypothetical: 2,000 HYPE principal, a 3.00% gross annual rate, 4.00% validator commission, a 30-day holding period, and no balance change during those 30 days.
Commission reduces the hypothetical annual rate to 2.88%: 3.00% × (1 − 0.04). Applying daily compounding gives 2,000 × (1 + 0.0288 ÷ 365) 30 − 2,000 = 4.7397 HYPE. The concrete hypothetical result is 4.7397 HYPE after 30 days. A real result moves when total network stake, commission, or the epoch-eligible balance changes.
The HYPE market price never enters this token-denominated calculation. Converting 4.7397 HYPE into another currency would introduce a separate, changing input.
Minimum epoch balance decides which HYPE earns
The staking reward schedule uses the minimum delegated balance recorded within each epoch. Hyperliquid epochs span 100,000 HyperBFT rounds, approximately 90 minutes on mainnet, while validator and consensus stakes remain static for that epoch. Adding HYPE midway does not raise that epoch's minimum; reducing stake lowers it.
Rewards accrue every minute, distribute once per day, and automatically redelegate to the chosen validator. Daily distribution supplies the compounding step, so there is no separate claim action for native rewards. The reward curve follows the same inverse-square-root idea used by Ethereum: higher total HYPE stake produces a lower network rate.
A published formula reference point pairs 400 million total HYPE staked with about 2.37% per year. That pair illustrates the curve rather than quoting a live yield. Rewards come from the future emissions reserve, and validator commission reduces what reaches the delegator. The reinvestment interval is protocol-driven rather than user-selected.
The validator's one-year bond is not your lockup
Validator self-delegation carries a 10,000 HYPE minimum and a one-year lock. Those terms belong to the operator's bond. An ordinary delegator keeps the separate 1-day validator lock and 7-day staking-to-spot queue; delegating to an operator does not inherit the operator's one-year commitment. The 10,000-HYPE threshold does not apply to ordinary delegators, as described in Using Hyperliquid.
If self-delegation drops below 10,000 HYPE, the validator becomes undelegate-only. Existing delegators can leave after their own lock expires, but the operator cannot attract fresh third-party delegation to rebuild total stake. That state is visible before a new allocation, making it a hard eligibility check rather than a soft preference.
Jailing converts validator uptime into missed rewards
Validator jailing removes an operator from HyperBFT consensus and stops rewards for its delegators. Peers cast jail votes when a validator fails to answer consensus messages with adequate latency or frequency. A quorum requires more than two-thirds of total stake, and reaching that quorum places the validator in jailed status.
A validator can unjail after correcting the operating issue, subject to onchain rate limits. Delegation does not automatically move during the interruption. Hyperliquid currently uses jailing without automatic slashing for ordinary consensus staking; slashing remains a separate concept reserved for provable behavior such as double-signing the same round. Commission and uptime therefore answer different questions: one reduces each reward, while the other determines whether a reward exists.
After the 1-day delegation lock expires, a delegator can respond by moving the allocation inside the staking account. The 7-day queue matters only if the destination is spot, not another validator.
Move HYPE into HyperCore before choosing a validator
The HyperCore staking balance is the staging area for native delegation. HYPE held on HyperEVM must first move to HyperCore, then from the HyperCore spot balance into the staking balance. The spot-to-staking transfer is instant. Only after that transfer does the wallet choose a validator and start its 1-day delegation lock.
The Hyperliquid interface, Nansen, Validao, and HypurrScan all expose native staking workflows over the same HyperCore state. Rabby, MetaMask, or a WalletConnect-compatible connection signs the wallet actions supported by the chosen interface. Switching interfaces does not shorten a lock or bypass the 7-day queue because those rules live in the protocol.
Developers can submit a token delegation action and read delegations, summaries, history, and rewards through the Hyperliquid API. Validator addresses use 42-character hexadecimal form. Node commands express native HYPE in 8-decimal smallest units, so 1 HYPE equals 100,000,000 units. Human-readable interfaces handle that conversion, but automated tooling must do it exactly.
Staked HYPE also changes the trading-fee tier
Hyperliquid staking tiers reduce trading fees independently of validator rewards. The schedule starts above 10 HYPE with a 5% discount, then above 100 HYPE with 10%, above 1,000 HYPE with 15%, above 10,000 HYPE with 20%, above 100,000 HYPE with 30%, and above 500,000 HYPE with 40%. Each cutoff is strict: holding exactly the threshold amount does not enter the higher tier. Validator commission never alters the tier; only attributed staked HYPE does.
The same wallet needs no account link. Separate staking and trading addresses require a two-step link: the trading user starts it, and the staking user finalizes it. That link is permanent, gives the staking user control of the trading account, and cannot be undone. After linking, the trading user receives the staking attribution while the staking user does not receive its own staking-related discount. Keep both roles on one address unless that permanent control relationship is intentional.
Hyperliquid staking FAQs
Must a delegator hold 10,000 HYPE?
No, the 10,000 HYPE threshold belongs to validator self-delegation, not an ordinary delegator. A holder moves the chosen amount from the HyperCore spot balance into the staking balance and delegates from there. The protocol's staking rules do not apply the validator threshold to users. Interface precision and the available staking balance still constrain the amount a wallet submits.
Does a validator take custody of delegated HYPE?
No, native delegation records stake against a validator without granting that validator spending authority over the wallet. The HYPE remains represented in the delegator's staking account, subject to the 1-day delegation lock and the separate 7-day route back to spot. The validator influences reward production and commission; the wallet owner signs undelegation and withdrawal actions.
Can staked HYPE be used as trading collateral?
No, HYPE assigned to the staking account is unavailable as spot inventory or trading collateral at the same moment. Moving it back to the spot balance requires undelegation first, followed by the 7-day staking withdrawal queue. Keep any HYPE needed for orders, transfers, or margin outside the delegated amount.
Are native staking rewards sent to a separate claimable balance?
No, native HyperCore rewards do not wait in a separate manual-claim balance. They accrue every minute, distribute daily, and automatically redelegate to the same validator. Making reward HYPE liquid therefore requires undelegating the desired amount, then transferring that undelegated balance through the 7-day queue to the spot account.
Which API record shows whether a staking withdrawal is pending?
The Hyperliquid Info API exposes pending withdrawal state through the delegator summary for a wallet address. The response separates delegated HYPE, undelegated HYPE, total pending withdrawal, and the number of pending withdrawals. Delegation history and reward records are separate queries, so an automated monitor can distinguish a validator change from an actual exit to spot.
Does native HyperCore delegation mint a liquid staking token?
No, native HyperCore delegation does not mint a liquid staking receipt token. The position remains an account-level delegation to a validator, and rewards automatically increase that delegation. A separate token offered by another protocol would carry its own contracts, liquidity, and redemption mechanics; it should not be treated as identical to Hyperliquid's native staking balance.