Overview
The Chorus One SDK simplifies staking on Hyperliquid, a high-performance Layer 1 blockchain powered by the HyperBFT consensus algorithm. This SDK enables developers to build staking applications that interact with Hyperliquid's unique account model and delegated proof-of-stake system.
Understanding Hyperliquid Staking
Account Model
Hyperliquid uses a dual-account structure similar to how USDC can be transferred between perpetuals and spot accounts:
Spot Account: Your main trading and holding account for HYPE tokens
Staking Account: A dedicated account for staking operations and delegations
Transfer Characteristics:
Spot β Staking: Instant transfers (no waiting period)
Staking β Spot: 7-day unstaking queue (maximum 5 pending withdrawals per address)
Delegation System
Hyperliquid implements delegated proof-of-stake with the following characteristics:
Delegation Mechanics:
1-day lockup period per validator delegation - Once you delegate tokens to a validator, you must wait 24 hours before you can undelegate those specific tokens. After the lockup expires, you can undelegate partially or fully at any time.
Undelegation is instant (tokens return to staking account immediately, not to spot)
You can delegate to multiple validators simultaneously
Minimum validator self-delegation: 10,000 HYPE
Reward Mechanics
Hyperliquid's staking rewards follow an Ethereum-inspired model:
Reward Formula:
Reward rate is inversely proportional to the square root of total HYPE staked
Rewards come from the future emissions reserve
Distribution Schedule:
Rewards accrue every minute based on validator performance
Distributed daily to all delegators
Auto-compounded to your delegated stake (no manual claiming required)
Based on minimum balance held during each staking epoch
Setting Up the Staker
To set up the Hyperliquid Staker, you need to specify the network chain:
Configuration Options:
chain:'Mainnet'|'Testnet'(required)
The staker uses Hyperliquid's REST API endpoints (/info and /exchange) and doesn't require RPC connections or additional configuration.
Getting the Validator Address provided by Chorus One
The @chorus-one/hyperliquid module includes the CHORUS_ONE_HYPERLIQUID_VALIDATOR constant, which contains the Chorus One mainnet validator address for building transactions.
Building Transactions
Hyperliquid transactions use EIP-712 typed data signing, which differs from standard Ethereum transactions. The SDK provides a three-step workflow:
Transaction Workflow
1. Build the unsigned transaction:
The SDK automatically converts the amounts in HYPE to Hyperliquid's 8-decimal wei format internally.
2. Sign the transaction:
All Chorus One signers (Fireblocks, Local, etc.) work seamlessly with the Hyperliquid SDK.
3. Broadcast the signed transaction:
Transaction Confirmation: Hyperliquid's API doesn't provide transaction status queries. Use getDelegatorHistory() to verify that your transaction was successfully processed.
Verifying Transaction Success
Since Hyperliquid doesn't support transaction status queries, verify using delegation history:
Staking Workflow Example
Here's a complete workflow showing how to stake HYPE tokens to a validator:
Common Operations
Query Staking Information
Unstaking Flow
To move staked tokens back to your spot account (two steps required):
Next Steps
Explore detailed method documentation in Methods
Review the HyperliquidStaker API Reference
Check out the example applications in the SDK repository
Further Reading
Last updated
Was this helpful?