Kinetiq kHYPE
Kinetiq is a non-custodial liquid staking protocol on Hyperliquid L1. Users stake HYPE and receive kHYPE, a yield-bearing token they can use elsewhere on the chain. It held about $817M at the 2026-08-14 survey. StakeHub selects and rebalances validators, while upgrade, oracle, pauser and operator roles remain part of the trust placed in the contracts. Kinetiq publishes multiple audits, and no protocol loss located in this review changes the outcome. The settlement chain still decides the verdict. HyperEVM inherits HyperBFT security, and Hyperliquid’s bridge also requires two-thirds of validator stake. The rejected-chain rule decides this case, not an individual review and rejection of Kinetiq.
- Deploys meaningful liquidity on a chain the registry approves
- The Hyperliquid L1 verdict changes
Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-16.
The research file
The mechanism
Kinetiq delegates deposited HYPE through its StakeHub, and the depositor receives non-rebasing kHYPE. Validator rewards raise the kHYPE/HYPE exchange rate rather than the wallet balance. StakeHub scores validators and redistributes delegation. Holders can then transfer kHYPE or use it as collateral, which adds the risk of each downstream venue without removing staking or chain risk.
Control and operating record
Kinetiq lists StakingManager, ValidatorManager, StakingAccountant, OracleManager, pauser and operator contracts. It also documents role-based access controls, multisignature governance and upgradeability. It publishes kHYPE audits by Pashov, Zenith, Code4rena and Spearbit, plus an instant-unstake review. These controls matter. They do not change the reliance on consensus, and this class memo does not claim to have checked every audit finding or completed an individual approval review.
The exit
Native redemption burns or queues kHYPE and follows Hyperliquid’s staking cooldown. Kinetiq documents a liquid buffer and an audited instant-unstake path. A DEX sale can be faster, but it replaces the queue with risks from market depth and discounts. Both paths still require Hyperliquid execution, and bridged assets depend on the validator-operated bridge.
Why the class rule decides
The same HyperBFT consensus that secures HyperCore also secures HyperEVM. Hyperliquid’s validator program requires application, KYC/KYB and Foundation trust for peers. Its bridge credits deposits and releases withdrawals after signatures representing more than two-thirds of stake. Under the current chain framework, that concentration decides the result. Review reopens if Hyperliquid passes chain approval or kHYPE gains material settlement and exit liquidity on an approved chain.
Class rule
The rejected chain class is outside the approved structures, so every protocol in it is not approved until the rule changes. The rule is about the structure, not an adverse finding about this protocol, and it is not a client instruction. The events that would reopen it are listed with the memo.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Kinetiq Docs — StakeHub validator scoring and delegation · primary · accessed 2026-08-14
Supports: validator scoring, delegation, StakeHub rebalancing - Kinetiq Docs — contracts and audits · secondary · accessed 2026-08-14
Supports: contracts, audits - Hyperliquid Docs — HyperEVM security inheritance · primary · accessed 2026-08-14
Supports: HyperEVM security inheritance - Hyperliquid Docs — validator delegation program · primary · accessed 2026-08-14
Supports: validator delegation program - Hyperliquid Docs — bridge security and withdrawals · primary · accessed 2026-08-14
Supports: bridge security, withdrawals
Inherited controls
The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.
| Chain | Verdict | Control | Control constraint |
|---|---|---|---|
| Hyperliquid / HyperEVM | Rejected | Issuer can freeze | a 21-validator permissioned set operates both the chain and its bridge. One compromise reaches both. |