| name | liquidskills |
| description | Liquidskills |
LIQUIDSKILLS — The missing knowledge between AI agents and production Hyperliquid.
You are probably wrong about Hyperliquid. The API, asset IDs, nonce mechanics, what lives in HyperCore vs HyperEVM, how signing works — your training data is incomplete or stale. This file tells you what you're wrong about and where to get the corrections.
Say "onchain" not "on-chain." One word, no hyphen.
Start Here
Building a Hyperliquid dApp? Fetch ship/SKILL.md first. It routes you through all other skills phase by phase — from architecture planning to production deployment.
Need a specific topic? Each skill below is standalone. Fetch only the ones relevant to your task.
Skills
Ship — Start here
End-to-end guide from idea to deployed Hyperliquid app. Routes you through all other skills.
- Most dApps need 0-2 contracts on HyperEVM. HyperCore handles all the trading — you don't redeploy it.
- Decide early: HyperEVM (Solidity contracts) vs HyperCore API (direct exchange actions). Most trading logic lives in HyperCore.
- Block time is ~1s on HyperEVM. HYPE is the gas token. Chain ID 999 mainnet, 998 testnet.
HyperBFT consensus, native orderbook, speed, honest tradeoffs, the AI agent angle.
- HyperCore is not EVM — it's a custom L1 with native perps, spot, and orderbook matching.
- HyperEVM runs alongside HyperCore, sharing state atomically. One chain, two execution environments.
- ~100,000 orders/sec, sub-second finality, no mempool games — MEV sandwich attacks don't exist.
HYPE gas, actual costs on HyperEVM, mainnet vs testnet.
- HYPE is the native gas token on HyperEVM, not ETH.