Hyperliquid WebSocket Reconnect and Order Book Recovery

A resilient reconnect design for Hyperliquid market-data and user-event streams.

Connection state

Track connected, stale, reconnecting and synchronized states. A socket being open does not prove data freshness.

Backoff

Use jittered exponential backoff with a ceiling. Avoid synchronized reconnect storms across workers.

Recovery

Re-subscribe, fetch authoritative state and reconcile open orders, fills and positions before enabling execution.

Observability

Measure disconnect frequency, recovery time, event age and missed-fill incidents. Stop quoting while state is uncertain.

Use this architecture in a Hyperliquid market-making bot with a dashboard.