Cobo Agentic Wallet
Back to Recipes
Hyperliquid Vault Strategy

Hyperliquid Vault Strategy

Deploy and manage Hyperliquid Vaults — automated strategy accounts where a leader agent trades on behalf of depositors.

CategoryTradingAutomation
ChainsHYPERLIQUID
C
Cobo· Author
32 views·0 uses

Overview

Deploy and manage Hyperliquid Vaults — automated strategy accounts where a leader agent trades on behalf of depositors.

Facts

•api.mainnet: https://api.hyperliquid.xyz
•vault info: POST /info {"type": "vaultDetails", "vaultAddress": "<address>"} — vault state, depositors, P&L
•vault trading: leader's EIP-712 signed actions trade on vault's behalf
•eip712_domain (mainnet): {"name":"Exchange","version":"1","chainId":1337,"verifyingContract":"0x0000000000000000000000000000000000000000"}
•eip712_domain (testnet): {"name":"Exchange","version":"1","chainId":998,"verifyingContract":"0x0000000000000000000000000000000000000000"}
•vaultTransfer usd field: integer dollar amount (not micro-units); 10000 = $10,000 USDC
•vault orders: target vault sub-account by signing with vault leader key; same order API as personal account

Typical Flows

Create vault (one-time setup):

1.Create sub-account via Hyperliquid interface or API — produces vault address
2.Configure vault parameters: name, description, leader profit share percentage

Deposit to vault — 1 signed action:

3.POST /exchange with action vaultTransfer:
json
{
  "action": {"type": "vaultTransfer", "vaultAddress": "<vault>", "isDeposit": true, "usd": 10000},
  "nonce": <timestamp_ms>,
  "signature": "<EIP-712 sig>"
}

Trade on behalf of vault — same as perp/spot:

4.Place orders targeting vault sub-account using vault address as the trading account
5.All standard order types (limit, market, trigger) available within vault context

Monitor vault performance — off-chain:

6.POST /info {"type": "vaultDetails", "vaultAddress": "<address>"} — query depositors, total equity, all-time P&L

Withdraw from vault — 1 signed action:

8.POST /exchange with action vaultTransfer:
json
{
  "action": {"type": "vaultTransfer", "vaultAddress": "<vault>", "isDeposit": false, "usd": 5000},
  "nonce": <timestamp_ms>,
  "signature": "<EIP-712 sig>"
}

Policy Controls

•Leader controls all trades: Vault depositors trust the leader (agent) with capital; reckless trading affects all depositors.
•Withdrawal queue: Withdrawals may be delayed if vault has open positions that would cause liquidation upon capital removal.
•Profit share is automatic: Leader's percentage is deducted on depositor withdrawals with profit; no manual claim needed.
•Liquidation risk applies to vault: Vault positions follow same margin rules as individual accounts; over-leveraging puts depositor capital at risk.
•Transparency: All vault trades are publicly visible on-chain; strategy logic is exposed to front-running.
•Vault address vs personal address: Ensure orders target correct account; trading on personal account when intending vault (or vice versa) is a common mistake.
•Not applicable for: direct personal account trading — use hyperliquid-perp-trade or hyperliquid-spot-trade; vault must be created via Hyperliquid interface before use
•Partial reference: use web search for vault creation details, profit-sharing mechanics, or up-to-date API specs

References

•Docs: https://hyperliquid.gitbook.io/hyperliquid-docs/llms.txt — REST/WebSocket API, EIP-712 action signing, order types, asset indices, vault operations.