What is Hypersonic?
On Hyperliquid, a block proposal reaches the network before an hl-node commits and executes that block. Trading systems that wait for the node's written block or execution results cannot inspect the proposed transaction order during that interval. Hypersonic gives those systems an earlier view by streaming decoded Hyperliquid activity directly to their applications over TCP from three assigned Tokyo IP addresses on port 4011. You do not need to run an hl-node to receive it.
The SUB direct feed first reports transaction bundles, then resolves the signer and master account behind them. When a block proposal arrives, it provides the bundle hashes in proposed execution order, so a client can match the proposal to bundles it has already received. The separate SUB bbo feed starts with a confirmed best bid and offer (BBO) snapshot, sends quotes predicted from proposals, and reports executed top-of-book changes through confirmation messages.
These streams let a client examine proposed order flow and top-of-book changes before execution completes. Proposals and optimistic quotes are early observations, not executed trades: Hypersonic does not provide order IDs, fills, balances, or full order book depth. Use an hl-node or a managed Hyperliquid endpoint when your application needs those results.
Where Hypersonic fits
Hyperliquid Peering supplies dedicated upstream connections to an hl-node that you operate. Hypersonic sends decoded data directly to your application, including observations made before that node finishes block execution. The practical differences are:
Scroll the table horizontally to compare all three options.
| Compare | Your own hl-node | Peering | Hypersonic |
|---|---|---|---|
| What connects | Your hl-node connects to peers you configure. | Your hl-node connects to three dedicated Tokyo sentry peer IPs. | Your application connects directly to three assigned Tokyo IP addresses on port 4011. |
| Node required | Yes. You operate the node. | Yes. You operate the node. | No. Your application consumes the streams directly. |
| Data delivered | Blocks and the mempool your peers pass; the node writes local files. | Blocks and the full raw mempool reach your node, which writes local files. | Decoded bundles, signer attribution, block proposals, and optimistic and confirmed top-of-book BBO reach your application. |
| Post-execution data | Process your node’s raw outputs for fills, order IDs, balances, and book depth. | Process your node’s raw outputs for fills, order IDs, balances, and book depth. | Use your own hl-node or a managed endpoint for these results. The BBO feed confirms top-of-book quotes. |
| Price | No Quicknode add-on fee; you pay for your own infrastructure. | $500 per month plus an active Quicknode plan and your own node. | $5,000 per month plus an active Quicknode plan; Peering is included. |
You can run both: use Hypersonic for early proposals and quotes, then use your node on the included Peering for post-execution state. A managed Hyperliquid gRPC endpoint is another source of post-execution data if you do not operate a node. Hypersonic itself does not supply exchange-assigned order IDs, individual fills, account balances, or order book depth beyond the best bid and offer.
Connect to the feeds
Quicknode gives you three Tokyo IP addresses for the TCP stream after activation. Quicknode allowlists the public source IPv4 address of each server that connects. Each allowlisted source IP can open up to two concurrent connections to each assigned stream IP: one for SUB direct and one for SUB bbo, or six connections across all three stream IPs. Stream usage is unmetered. Use the current IP addresses supplied by Quicknode; they are not static.
Open a plain TCP connection to an assigned IP on port 4011, then send one newline-terminated subscription command. Enable TCP_NODELAY in a production client. Open separate connections to consume both feeds. The feeds share a port but use different encodings:
| Feed | Encoding | What you receive |
|---|---|---|
| SUB direct | Framed Protocol Buffers | Pre-confirmed transaction bundles, signer attribution, and ordered block proposals. |
| SUB bbo | Newline-delimited JSON | A confirmed top-of-book snapshot, optimistic quotes, and post-execution confirmations or corrections. |
For BBO, add a comma-separated list of markets to the command, such as SUB bbo BTC,ETH. The feed also accepts the selectors all, all-perps, all-hip3, all-spot, and all-outcomes. Quicknode provides your assigned stream IPs and direct_stream.proto during activation.
Send the subscription as a newline-terminated line on its own connection:
SUB direct
SUB bbo BTC,ETH
Send the command within 250 ms of opening the connection. Each direct frame has a four-byte, big-endian length prefix followed by a 17-byte header and a Protobuf StreamMessage. The length counts the header and Protobuf message, and a frame can be up to 64 MiB. The header contains a one-byte message kind, an eight-byte emit_ns, and an eight-byte ref_ns, both big-endian nanosecond timestamps. Kind 1 identifies MempoolBundle, 2 identifies Block, and 3 identifies BundleSigners. Use the supplied direct_stream.proto for field definitions when implementing the TCP reader.
To check connectivity from an allowlisted Linux server, replace YOUR_ASSIGNED_STREAM_IP with one of the stream IPs Quicknode sent you. This Bash probe prints the first BBO snapshot and exits; it does not need direct_stream.proto.
HYPERSONIC_HOST="YOUR_ASSIGNED_STREAM_IP" timeout 10s bash -c '
exec 3<>/dev/tcp/$HYPERSONIC_HOST/4011
printf "SUB bbo BTC\n" >&3
IFS= read -r line <&3
printf "%s\n" "$line"
exec 3<&-
'
Reading SUB direct
The direct feed exposes three stages of the same flow. MempoolBundle carries a decoded transaction bundle when it is first seen. BundleSigners follows with the recovered signer and associated account information. Block carries an ordered block proposal and the hashes of the bundles it references.
A client can retain bundles and signers by hash and look up each Block proposal's bundle_hashes in order. Signer information may arrive after its bundle, so join those messages when both are available. A proposal is an early view of a block; do not treat it as a record of completed execution. The next Block provides a finality signal when its parent_round equals the earlier proposal's round. This signal still does not include fills or other execution results.
Each MempoolBundle includes first_seen_ns (when Quicknode first saw it in Tokyo) and emit_ns (when it was sent). BundleSigners repeats those fields for the associated bundle. A Block includes block_time_ns (the consensus timestamp), recv_ns (when Quicknode received the proposal), and emit_ns. These timestamps are Unix nanoseconds. Block.round identifies the proposal, while parent_round identifies the round it extends. Consensus rounds can be skipped, so do not assume consecutive round numbers; compare the next block's parent_round with the prior block's round when checking continuity.
In BundleSigners.signers[], user is the recovered signer, which may be an API agent wallet. account is the master account, vault, or sub-account it acts for. The corresponding action's optional vault_address identifies a vault or sub-account when one is named. Entries in signers[] follow the order of MempoolBundle.actions[].
To verify that SUB direct returns binary frames, run this Bash probe from an allowlisted Linux server:
HYPERSONIC_HOST="YOUR_ASSIGNED_STREAM_IP" timeout 10s bash -c '
exec 3<>/dev/tcp/$HYPERSONIC_HOST/4011
printf "SUB direct\n" >&3
head -c 32 <&3 | od -An -tx1
exec 3<&-
'
The first four bytes are the frame length, and the fifth byte is the message kind (01, 02, or 03). This probe does not decode the Protobuf payload. Use the supplied direct_stream.proto with your client language to decode StreamMessage. A production client should connect to all three stream IPs and deduplicate bundles by hash and blocks by round.
Reading SUB bbo
The BBO feed starts with a snapshot of confirmed top-of-book prices and sizes for the subscribed markets. A new market may also produce a snapshot while the connection is open. An optimistic event predicts both prices and sizes (bid_px, bid_sz, ask_px, ask_sz) when a proposal changes a market's predicted quote. After execution, a confirm event reports a changed or corrected confirmed quote for that market; it can arrive without a preceding optimistic event. A status event reports a pause, resumption, or reseed.
Keep optimistic and confirmed quotes distinct in your application. Apply every confirm to your confirmed top of book, including when no optimistic quote preceded it. The BBO feed covers top-of-book only; it is not a full order book.
The following illustrative JSON lines show the event sequence for one market:
{"type":"snapshot","coin":"BTC","confirmed_height":100000,"confirmed_time_ns":1763251200000000000,"bid_px":"90000.0","bid_sz":"1.25","ask_px":"90001.0","ask_sz":"0.75","emit_ns":1763251200001000000}
{"type":"optimistic","coin":"BTC","proposed_round":200000,"block_time_ns":1763251200067000000,"confirmed_height":100000,"confirmed_time_ns":1763251200000000000,"pending_blocks":1,"complete":true,"bid_px":"90002.0","bid_sz":"1.50","ask_px":"90003.0","ask_sz":"0.50","emit_ns":1763251200080000000}
{"type":"confirm","coin":"BTC","confirmed_height":100001,"confirmed_round":200000,"block_time_ns":1763251200067000000,"matched":true,"correction":false,"bid_px":"90002.0","bid_sz":"1.50","ask_px":"90003.0","ask_sz":"0.50","emit_ns":1763251200150000000}
Here, the confirm event reports that the predicted bid and ask prices matched execution. matched describes the price prediction; use correction to determine whether to replace your current quote. The following illustrative correction has matched: false and carries the executed prices and sizes:
{"type":"confirm","coin":"BTC","confirmed_height":100004,"confirmed_round":200004,"block_time_ns":1763251200402000000,"matched":false,"correction":true,"bid_px":"89999.0","bid_sz":"0.80","ask_px":"90001.0","ask_sz":"1.10","emit_ns":1763251200480000000}
Always apply a confirm with correction: true, including when matched is null because there was no prior optimistic score. proposed_round and confirmed_round identify the proposal and executed round. Track confirmed_height monotonically per market, but do not require consecutive heights: quiet blocks may have no confirm for that market. Timestamp fields are Unix nanoseconds: block_time_ns is the consensus timestamp, confirmed_time_ns is the timestamp of the last confirmed block in a snapshot or optimistic event, and emit_ns is when the message was sent.
How to handle the feeds
pending_blocks counts proposals ahead of the last confirmed height. An optimistic quote with complete: false was calculated before all bundle bodies were available; a later update for the same proposed_round can have complete: true.
Do
- Keep optimistic and confirmed quotes separate. Apply every
confirm, including one withcorrection: trueor no preceding optimistic quote. - Stop acting on optimistic quotes from a stream IP while its
statusreportsstate: paused. Resume only after that IP reportsresumedorreseeded. - Deduplicate
MempoolBundleandBundleSignersby bundle hash andBlockby round across the three stream IPs. Keep the first arrival measured at your client.
Don't
- Treat
complete: falseas final or replace a market's confirmed BBO with one from a lowerconfirmed_height. - Compare
emit_nsvalues from different stream IPs to decide which message arrived first, or assume every BBO confirmation has the next consecutive height. - Use optimistic quotes for fills, order IDs, balances, or position accounting. Confirmed BBO covers executed top of book; use your own
hl-nodeor a managed Hyperliquid gRPC endpoint for those other results.
Reconnect and keep up with the stream
Hypersonic streams current events only. After a disconnect, reconnect and use the new BBO snapshot to reestablish confirmed state; missed events are not replayed. The streams have no ping/pong heartbeat frames. On a quiet single-market BBO subscription, enable TCP SO_KEEPALIVE to detect a dead connection. Keep reading from each connection so the client does not fall behind: a reader that stops draining TCP for 20 seconds or falls 4,096 messages behind is disconnected. Quicknode recommends sizing for approximately 200 Mbps per stream IP during the US market open.
Connection troubleshooting
- Connection times out: Check that the public source IPv4 address seen by Quicknode is allowlisted and that your server can make outbound TCP connections to port
4011. If the server uses NAT, register its public egress IP. - Connection closes immediately: Send a valid newline-terminated
SUB directorSUB bbocommand within 250 ms, and check that you have not exceeded two connections from the same source IP to that stream IP. - BBO sends a snapshot but few updates: An
optimisticmessage is emitted only when the predicted top of book changes for a subscribed market. Try an active market such asBTCwhen checking the feed. - Direct frame length looks invalid: Read
SUB directas length-prefixed binary data. Use a newline-delimited JSON reader only forSUB bbo.
How to connect to Hypersonic in four steps
Hypersonic is manually provisioned. Complete the account and server registration steps before connecting from your Tokyo servers.
- Add Hypersonic to your accountCreate a Quicknode account and add Hypersonic for Hyperliquid for $5,000 per month. If you want to test it first, ask Quicknode about a complimentary trial. View the add-on.
- Open a support ticketProvide your Quicknode account email and the public IPv4 address of each Tokyo server that will connect. A Quicknode engineer will handle provisioning. Open a ticket.
- Quicknode allowlists your IPsQuicknode allows the public source IPs of your servers through its firewall and sends your three assigned stream IPs and direct_stream.proto.
- Connect to all three stream IPsConnect directly to each assigned IP on port 4011 and send SUB direct within 250 ms. Use a second socket per IP for SUB bbo if you need top-of-book quotes. Deduplicate bundles by hash and blocks by round using the first arrival at your client.
If a server's public IP changes, contact support to update the allowlist before that server connects from the new address.
Pricing and support
Hypersonic costs $5,000 per month and requires an active Quicknode plan. The price includes the unmetered direct and BBO feeds and Hyperliquid Peering at no additional charge. A complimentary trial may be available for qualified trading teams; contact support to confirm eligibility.
For current product details, see the Hypersonic product page. For provisioning, connectivity, or stream questions, email support@quicknode.com or use your dedicated Quicknode channel.