Understand the data you receive from the Orderbook WebSocket, including response formats, deduplication behavior, and the difference between Standard and HFT modes.
BBO Response Format
BBO payload
Order Updates Response Format
orderUpdates payload
Deduplication
The server automatically deduplicates data to minimize bandwidth and processing overhead.
Type | Behavior |
|---|---|
BBO | Only sends when bid/ask price or size changes (~1μs overhead) |
L2Book | Only sends when snapshot hash changes (~10μs overhead) |
Trades | Only sends on fills — no empty messages |
Standard vs HFT Mode
HypeRPC offers two modes. Standard mode batches updates by block, while HFT mode streams events individually for the lowest possible latency.
Feature | Standard | HFT Mode |
|---|---|---|
Update frequency | ~2/sec (block rate) | ~100+/sec (streaming) |
BBO latency | ~500ms | ~100ms |
Processing | Block-synchronized | Event-by-event |
L4Book | Full support | Streaming diffs |
Compression | zlib (optional, ~80% savings) | Disabled for speed |
Tip
HFT mode is recommended for market makers and algorithmic trading systems where every millisecond counts. Standard mode is ideal for dashboards, analytics, and general monitoring.
Supported Markets
Market | Description | Examples |
|---|---|---|
Perpetuals | Perpetual futures contracts | BTC, ETH, SOL, HYPE |
Spot | Spot trading pairs | PURR/USDC, @-prefixed coins |
HIP-3 | HIP-3 DEX markets | X:Y format (e.g., xyz:TSLA) |