Kinetiq kHYPE
Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.
Kinetiq is a non-custodial liquid staking protocol on Hyperliquid L1: users stake HYPE and receive kHYPE, a yield-bearing token usable 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 contract trust model. Kinetiq publishes multiple audits and no protocol loss located in this review changes the outcome. The verdict is still the settlement chain’s: HyperEVM inherits HyperBFT security and Hyperliquid’s bridge also requires two-thirds of validator stake. This is a rejected-chain disposition, not an individually researched rejection of Kinetiq.
- Deploys meaningful liquidity on a chain the registry approves
- The Hyperliquid L1 verdict changes
The research file
The mechanism
Deposited HYPE is delegated through Kinetiq’s StakeHub and the depositor receives non-rebasing kHYPE. Validator rewards increase the kHYPE/HYPE exchange rate rather than the wallet balance. StakeHub scores validators and redistributes delegation; kHYPE can then be transferred or used as collateral, which adds the risk of each downstream venue without removing staking and chain risk.
Control and operating record
Kinetiq lists StakingManager, ValidatorManager, StakingAccountant, OracleManager, pauser and operator contracts, and 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 are meaningful controls. They do not change the consensus dependency, and this class memo does not claim to have completed a finding-by-finding audit verification or 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 substitutes market depth and discount risk for the queue. Both paths still require Hyperliquid execution, and bridged assets depend on the validator-operated bridge.
Why the class rule decides
HyperEVM is secured by the same HyperBFT consensus as HyperCore. Hyperliquid’s validator program requires application, KYC/KYB and Foundation trust for peers, while its bridge credits deposits and releases withdrawals after signatures representing more than two-thirds of stake. Under the current chain framework that concentration is dispositive. Review reopens if Hyperliquid passes chain approval or kHYPE gains material settlement and exit liquidity on an approved chain.
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 verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.
| Chain | Verdict | Grade | Control constraint |
|---|---|---|---|
| Hyperliquid / HyperEVM | Rejected | freezable | a 21-validator permissioned set operates both the chain and its bridge — one compromise reaches both. |