HIP-4 documentation
Exploratory documentation — not official Hyperliquid documentation.
API & data — overview
This page is a compact map: endpoints, channels, L1 action names, infra. It does not duplicate full request/response payloads.
For GitBook-style tables and JSON tabs, use Info endpoint.
Start here
- Info endpoint (GitBook-style) — outcomeMeta, candleSnapshot, userFees, userFillsByTime, WS examples, outcome types, coin mapping.
- Trading fees (L1) — proof chain: SetOutcomeFeeScale, spot rails, normalized fills vs
userSpotCrossRate. - Official layout reference: Hyperliquid Spot — Info endpoint.
Base URLs
Mainnet
- REST
https://api.hyperliquid.xyz/info - WebSocket
wss://api.hyperliquid.xyz/ws
Coin IDs
Critical for candleSnapshot and book subscriptions:
YES coin = "#" + (outcomeId × 10); NO coin = "#" + (outcomeId × 10 + 1). Example: outcome 2243 → #22430 / #22431.
WebSocket channels (summary)
Channels we used for live HIP-4 book and mark research. Detail and subscribe examples on Info endpoint.
L1 action types
High-level type strings seen in explorer / research. Full JSON payloads: HIP4-research-complete.md.
Examples for registerTokensAndStandaloneOutcome and VoteGlobalAction in the markdown file above.
System wallets
Eight linked Core addresses traced as one cluster; two roles mapped (HIP-4 operator + oracle), six unmapped. Testnet only — mainnet distribution unknown. None overlap the HyperEVM parimutuel deployer — see HyperCore (L1).
S3
Datasets and paths referenced in research (fills, EVM blocks). Requester pays where noted.