SpaceX lists on Nasdaq this week in what is expected to be the largest public offering on record. For most of the run-up, the most liquid open venue for price discovery on the company was not a private secondary desk. It was a perpetual futures market on Hyperliquid.

The SPCX perp launched on May 17 through trade.xyz, one of Hyperliquid's permissionless market deployers, with a reference price implying a valuation near $1.8 trillion. By IPO week, SpaceX perps had cleared roughly $2.2 billion in cumulative volume with more than $215 million in open interest across venues. Anthropic and OpenAI markets trade the same way ahead of listings expected later this year, and pre-IPO perp volume on Hyperliquid grew more than tenfold in three months. When Cerebras went public, its Hyperliquid perp had priced the debut within a few percent of the Nasdaq opening print. These markets produce real price signals.

They also produce access. Pre-IPO upside historically belonged to venture funds, insiders, and accredited secondary buyers. On Hyperliquid, exposure to the same names trades 24/7 from a wallet, independent of geography, brokerage menus, or accreditation status. The instruments are synthetic perps. They provide price exposure, not share ownership, and they carry the leverage and thin-liquidity risk that comes with synthetic markets. The access layer changed anyway.

One chain, every market

Hyperliquid stopped being a crypto-only exchange in October 2025. HIP-3 lets any builder who stakes 500,000 HYPE deploy a perp market on HyperCore. The builder selects the assets, oracles, leverage, and fees; the protocol handles matching, margining, and liquidation. The result is a permissionless listing venue. Nasdaq index futures, gold, FX, tokenized equities, and pre-IPO names now trade alongside crypto perps. HIP-3 markets have processed more than $120 billion in volume since launch, and at points this spring they approached half of total platform volume. HIP-4 followed in May 2026 with fully collateralized outcome markets: prediction markets, settled onchain.

Now any asset class that wants 24/7 settlement and open access ends up with a market here, and anyone with the stake gets to list the next one.

The data underneath is bespoke

HyperCore, the engine where all of this trading happens, is not an EVM. There are no standard event logs and no ABIs. Order book state, fills, funding payments, liquidations, vault operations, and ledger events each have their own raw structure. Reading them means writing decoding logic per event type, and the surface grows without anyone's permission: every new HIP-3 deployer adds markets, every HIP-4 listing adds outcome contracts.

The public API exists, but it is rate-limited, paginated by recency, and shallow on history. That is workable for a hobby dashboard. It is not workable for production, and it fails hardest exactly when the data matters most. In late May, a SpaceX perp dropped 45 percent in roughly thirty minutes as thin liquidity gave way, liquidating more than $1.5 million in positions. An application reading stale or partial data through that window is wrong at the moment its users most need it to be right.

Two specialists decode it

GoldRush, Covalent's data platform, does the HyperCore decoding work at multichain scale. Raw events come out as typed, structured records. Its streaming API covers OHLCV across Hyperliquid markets, including HIP-3 equities and commodities and HIP-4 outcome markets, with real-time multi-wallet tracking, no rate limits, and Tokyo-region nodes placed next to Hyperliquid's validators for latency. HyperEVM is indexed from genesis.

Hydromancer is the Hyperliquid-native specialist, built only for this chain: granular order book snapshots, every fill including liquidations, TWAPs, and ADLs, coverage across HIP-3 deployers and HIP-4 outcomes, deep historical archives, and endpoints rebuilt beyond the native schema. More than 80 teams run on it, and it appears in Hyperliquid's own builder documentation.

Both are strong at different things. Neither alone covers every market, endpoint, and data shape on a chain where listing is permissionless.

Uniblock routes across both

Both providers are live behind one Uniblock key. Each request is routed to the provider best positioned to serve it, responses come back in one normalized shape, and when a provider degrades, routing absorbs it before the application notices. One subscription, one dashboard, one bill, instead of separate accounts, separate rate-limit policies, and separate invoices.

This is the structural argument for aggregation on Hyperliquid specifically. Permissionless market creation means coverage gaps are inevitable for any single provider; some new HIP-3 market will always be indexed by one vendor first. Routed access turns those gaps, and provider incidents during the exact volatility spikes that make this chain interesting, into routing decisions instead of application rewrites. Retry logic, schema reconciliation, and status-page monitoring live in the routing layer. We watch it so the application does not have to.

Agents were the deciding factor

The heaviest consumers of Hyperliquid data increasingly are not humans. Trading agents, risk monitors, and portfolio trackers run continuously and call APIs at machine rates. An agent does not read a status page, rotate a key, or reconcile two response formats. For an autonomous consumer, decoded data and automatic failover are not conveniences. They are the difference between an agent that works and one that fails silently.

Structured records from GoldRush and Hydromancer, served through one normalized, self-healing routing layer, is what agent-ready means on this chain.

Live now

Hyperliquid keeps listing new markets. The decoding surface keeps compounding. The full surface, GoldRush and Hydromancer included, is served through a single Uniblock key today. Start at uniblock.dev; the Hyperliquid endpoints are in the docs.