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’sDocumentation Index
Fetch the complete documentation index at: https://goldrush.dev/docs/llms.txt
Use this file to discover all available pages before exploring further.
walletTxs subscription has zero rate limits and scales to thousands of concurrent wallet subscriptions on a single connection.
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
liquidationblock 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 onHypercoreFillTransaction, 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 onHypercoreFillTransaction 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 periodicclearinghouseState calls to maintain accurate per-wallet position state without polling between fills.
Scaling
| Scale | Approach |
|---|---|
| Up to ~1,000 wallets | One subscription with the full address list. |
| 1,000 – 10,000+ wallets | Shard across multiple subscriptions on the same connection. The SDK reuses one WebSocket. |
| Live cohort changes | Unsubscribe and resubscribe with the new address list - no need to tear down the connection. |
Related
HypercoreFillTransaction- full type reference.HypercoreLedgerEvent- vault, staking, borrow/lend, rewards subtypes.- Liquidations and vault events - full decoded-event walkthrough.
- Wallet Activity Stream - subscription reference.