Hyperliquid WebSocket

⚠️ **Trading warning / Avertissement trading** : informational only, not investment advice. A live feed feels authoritative, but a silently dropped socket looks exactly like a quiet market; acting on data you believe is live when it is stale can lose money fast. This skill is read-only and cannot place an order, and no stream here promises a return. Curated by Skill Harbor: the WebSocket skill of HyperGrok, Galleon Labs' seven-agent trading desk for Hyperliquid, covering both networks' socket endpoints and the subscribe, unsubscribe, ping and pong protocol with its per-IP limits (10 connections, 1000 subscriptions, 2000 messages per minute, and a server that closes a connection silent for 60 seconds). The subscription table is the core reference: all mids, the order book with its push cadence, trades, candles that update in place until the bar closes, best bid and offer, per-market asset context, and the per-account streams (fills, order updates, account events, funding, per-market account data, account state and open orders, TWAP state, and the heavy frontend snapshot), plus the ability to post info requests over the socket itself. Working examples come in three forms: raw socket frames, the official Python SDK, and the TypeScript client which reconnects and resubscribes by default. The Python caveats are unusually honest and worth the listing on their own: the SDK manager pings for you but does not reconnect on a drop, several subscription types are acknowledged by the server yet silently dropped by the Python SDK, and one legacy stream name is rejected by the live server outright, so the skill tells you which client to use for which stream. The watch pattern structures every watch as subscribe, log everything to a file with UTC timestamps, evaluate the condition, alert once with value, threshold, source and time, and never call the exchange endpoint. The recovery section is the safety core: on any disconnect, stale heartbeat or restart, record the last good time, alert unavailable, pause new-risk sends, re-establish subscriptions, then reconcile account state, open orders, outstanding order statuses and fills over an overlap window, de-duplicated by time, coin and fill id, before new risk is allowed again. From the galleonlabs/hypergrok-trading-desk repository (MIT). Honest caveats: the first fills message on a subscription is a snapshot of old fills, not news, and a restarted watch proves nothing about the gap until the recovery reads are done. Skill Harbor never reviews the code, review it yourself before use.