Skip to main content
The public Hyperliquid WebSocket caps you at 1000 subscriptions per IP, and every REST endpoint is weight-rate-limited per IP and per address. That’s nowhere near enough to track every active trader on Hyperliquid in real time - exactly what copy-trade, whale alerts, and “follow the flow” features need. GoldRush’s walletTxs subscription has zero rate limits and scales to thousands of concurrent wallet subscriptions on a single connection.

No public “all users” or leaderboard endpoint

Hyperliquid’s public /info API has no endpoint that lists every user, and the leaderboard you see in the frontend is backed by an internal endpoint that isn’t part of the documented API - so there’s no supported way to enumerate or scrape all addresses upstream. GoldRush gives you two supported paths instead:
  • Discover active traders in real time. The allFills channel streams every fill on HyperCore across every wallet - each entry carries the trader’s address, so the live tape doubles as a rolling census of who is active right now. liquidationFills does the same for every liquidation.
  • Follow a cohort at scale. Once you have a set of addresses (top traders, whales, a copy-trade list), the walletTxs firehose below streams all of their activity over a single connection with no per-IP or per-address limit - something the public 1000-subscription cap makes impossible.

What you get

  • One connection, many wallets. Pass an array of wallet addresses; updates for any of them come through the same stream.
  • Pre-decoded events. Fills, funding, vault actions, ledger events, deposits, withdrawals, and delegations come through as typed GraphQL union members - no parsing.
  • Liquidation context inline. When a fill is part of a liquidation, the liquidation block is attached directly.
  • Sub-second latency. Tokyo-colocated, validator-peered ingestion.

Subscribe

Patterns

Copy-trading

Subscribe to a curated list of high-PnL wallets. Filter the incoming stream on HypercoreFillTransaction, then mirror the coin, side, and size to your own execution layer.

Live whale feed

Subscribe to the top-N wallets by balance or notional position. Display every fill, liquidation, and large transfer in a chronological tape.

Liquidation alerts

Filter the stream on HypercoreFillTransaction events where liquidation is non-null. Push the event payload to a notification channel (Discord, Telegram, push). Each event includes the liquidated user, mark price, and method (Market vs Backstop).

Position monitoring

Pair the stream with periodic clearinghouseState calls to maintain accurate per-wallet position state without polling between fills.

Production considerations

The happy-path example above is enough to prototype. Three things to add before shipping:
  • Reconnect on close or error. The complete callback fires on a clean stream close; error fires on transport errors. In both cases, re-invoke the subscribe function with backoff so the firehose self-heals after network blips:
TypeScript
  • Validate addresses up front. Malformed wallet addresses can surface via error and tear down the whole subscription. Pre-filter the input list with /^0x[a-fA-F0-9]{40}$/ (or your library’s validator) before passing it in.
  • No gap-fill on reconnect. The subscription delivers events from the moment it opens - events that occurred during a disconnect are not replayed. For continuity across the gap, query userFillsByTime over the disconnect window after reconnecting.

Scaling

For very high fan-out, contact us about dedicated capacity.

Pair address format

Hyperliquid markets use a deployer-prefix naming scheme. The exact string differs by surface, so pass the value each API expects - matching is case- and format-sensitive.
  • deployer - wallet address of the HIP-3 builder that deployed the market. Omitted for canonical Hyperliquid markets.
  • symbol - market ticker (e.g. GOLD, OIL).
  • quote - the margin / quote currency, usually USDC (some HIP-3 markets use USDH).
HIP-4 outcome markets use a separate #<encoding> scheme (e.g. #1230), not the deployer-prefix - see HIP-4 Markets.
Discovering markets: a dedicated market-list endpoint (the perpDexs Info API type) is on the roadmap. Until it ships, call metaAndAssetCtxs - the name field on each universe entry is the canonical pair address.
  • HypercoreFillTransaction - full type reference.
  • HypercoreLedgerEvent - vault, staking, borrow/lend, rewards subtypes.
  • Liquidations and vault events - full decoded-event walkthrough.
  • Wallet Activity Stream - subscription reference.