The problem
The public Hyperliquidinfo API is free, generous, and self-serve. That’s why almost every Hyperliquid wallet, dashboard, and trading app on the market looks the same: a thin wrapper around info endpoints, a chart from candleSnapshot, and a fills tab that runs out at 10,000 rows.
If your product is the data, and the data is a commodity, you’re competing on UI alone. That’s a losing race.
This page walks through six things you can build with GoldRush that you cannot build (or cannot build cheaply, or at scale) on the public Hyperliquid API. They are ordered by immediate impact on user growth and retention, not by technical novelty. Start at the top.
1. Real-time wallet firehose with zero rate limits
The public WebSocket caps you at 1000 subscriptions per IP, and every REST endpoint is weight-rate-limited per IP and per address. That is nowhere near enough to track every active trader on Hyperliquid in real time, which is exactly what copy-trade, whale alerts, and “follow the flow” features need. Once your user count hits the low thousands, you are sharding IPs, queueing requests, or backing off. GoldRush’swalletTxs subscription has zero rate limits and scales to thousands of concurrent wallet subscriptions on a single connection, running on Tokyo-colocated, validator-peered infrastructure.
Build: copy-trading, live whale-feed pages, “who is adding or closing positions right now,” cohort dashboards, all without ops overhead.
Start with: Wallet Activity Stream.
2. Pre-decoded events for liquidations, vaults, staking, and delegation
The public API surfaces raw building blocks; you write the parser. Liquidations are buried inside fills as a thin stub, and vault, staking, and delegation activity arrives as untyped ledger updates you have to classify yourself. GoldRush ships every one of these pre-decoded and typed:- Liquidations with the liquidated user, mark price, method (Market vs. Backstop), leverage type, account value, and the full liquidated-positions list, inline with the fill.
- Vaults, staking, delegation, borrow/lend as 20+ named subtypes:
LedgerVaultDeposit,LedgerVaultWithdraw,LedgerVaultLeaderCommission,LedgerVaultDistribution,HypercoreDelegationEvent, validator rewards,LedgerCStakingTransfer,LedgerBorrowLend, and more.
HypercoreFillTransaction, HypercoreLedgerEvent.
3. Show users their full trading history, not the last 10,000 fills
userFills caps at ~10,000 rows per address. Active traders blow through that in weeks. Users notice when their PnL chart starts in the middle of last quarter.
GoldRush retains every fill, every funding payment, and every ledger event going back to HyperCore block 676607001 (2025-07-27T01:49:59 UTC). Pull it as a historical range or stream it forward in real time. (HyperEVM coverage goes all the way back to genesis.)
Build: lifetime PnL charts, tax exports, “your first trade was…” retention hooks, year-in-review screens.
Start with: HypercoreFillTransaction, HypercoreFundingEvent, or warehouse delivery via the Pipeline API (hl_fills, hl_funding).
4. Live candles and discovery for every HIP-3 market
HIP-3 lets builders deploy their own perp markets (equities, commodities, niche assets), and new ones appear constantly. The publiccandleSnapshot is poll-based and effectively limited to mainstream markets, and discovering HIP-3 markets means stitching market IDs by hand.
GoldRush’s ohlcvCandlesForPair and ohlcvCandlesForToken are real-time WebSocket streams that address HIP-3 markets natively with the deployer-prefix syntax (xyz:GOLD-USDC, flx:OIL-USDH). List, chart, or stream any market the moment it goes live.
Build: a “new markets” tab, deployer-scoped leaderboards, alerts when a new market opens, multi-pane dashboards, a chart widget that “just works” on xyz:GOLD-USDC without special-casing.
Start with: OHLCV Pairs Stream, OHLCV Tokens Stream.
5. Land Hyperliquid data directly in your warehouse
User analytics, retention cohorts, churn modeling, and revenue attribution all live in your data warehouse, not in REST responses. Building that pipeline against the public API means writing your own ETL, your own backfill, your own schema, your own retry logic. GoldRush’s Pipeline API streams Hyperliquid into ClickHouse or BigQuery as normalized tables:hl_fills, hl_trades, hl_orders, hl_funding, hl_deposits, hl_withdrawals, hl_delegations, hl_validator_rewards, hl_ledger_updates. No ETL on your side.
Build: product analytics on real onchain behavior, A/B-test impact on trading volume, internal whale-watching for BD, churn models tied to actual PnL.
Start with: Pipeline API: Hyperliquid normalizers, Stream Hyperliquid trades to ClickHouse.
6. Cover the rest of the wallet beyond HyperCore
Once the trading surfaces above are working, the obvious next gap is everything that lives off HyperCore. The public Hyperliquidinfo API has no concept of HyperEVM (chain 999), where DEXes, NFT mints, and lending protocols live, and no concept of any other chain a user might hold assets on.
GoldRush covers HyperEVM with the same shape as every other EVM chain (token balances, ERC-20 transfers, approvals, NFTs, gas, blocks), and gives you the same address across 100+ chains under one API key.
Build: a real “Wallet” tab for HyperEVM, an approvals revoke flow, NFT galleries, and a unified portfolio view that follows the user wherever they hold assets.
Start with: HyperEVM chain page, Get token balances for address.
Where to start
The fastest paths from “commodity wrapper” to “feature your competitors don’t have”:Smart-money firehose
Subscribe to thousands of whale wallets in one connection. Powers copy-trade and live whale-feed pages.
Liquidation feed
Pre-decoded liquidations with mark price, method, leverage, and full position context. Ready for push notifications.
Vault and staking events
20+ typed ledger event subtypes for vaults, staking, delegation, borrow/lend, and rewards.
Pipeline API for analytics
Land normalized Hyperliquid tables in your warehouse for retention cohorts and revenue analytics.