DUAL-ENGINE STREAM LIVE — <5ms INTERNAL FANOUT SLA

Institutional WebSocket & REST API

Zero-polling raw JSON feed for algorithmic trading systems and HFT execution desks. Streams Binance Futures liquidation cascades, CVD divergences, and Hyperliquid L1 on-chain mega-whale liquidations in real time.

⚡ Engine 1: Whale Core v9.0

Direct connection to 100 Binance Futures perpetuals. Emits LIQ_CASCADE, VOL_SPIKE, WALL_SWEEP, OI_EXPLOSION, and BTC_DECOUPLING.

🐋 Engine 2: Whale Sonar v9.2

Hyperliquid L1 On-Chain Perp DEX daemon. Continuously tracks top-30 mega-whales, emitting WHALE_LIQ_DANGER (≤5% to liquidation) and WHALE_POSITION_INFLOW ($1M+ scale-in).

⚡ What is Whale Core & Whale Sonar B2B Stream?

Whale Core & Whale Sonar B2B API is an institutional market data pipeline operating via in-memory Redis Pub/Sub. It computes real-time quantitative order flow anomalies across 100 Binance Futures pairs and monitors top-30 Hyperliquid on-chain whale wallets. Pushes structured JSON payloads to algorithmic clients in under 5 milliseconds with zero HTTP polling bottlenecks and zero rate-limit drops.

< 5 ms
Internal Latency

Zero-delay broadcast from Redis Pub/Sub memory directly to active WebSocket subscribers.

100 + 30
Markets & Whales

100 Binance Futures perpetuals + top 30 Hyperliquid L1 on-chain mega-whale addresses.

7
Anomaly Types

5 Binance order flow anomalies + 2 Hyperliquid on-chain whale alerts in a unified JSON format.

WSS + REST
Dual Protocol

Persistent WebSocket push stream plus instant REST snapshot endpoints for recent events.

Real-Time JSON Payload Specifications

Select an event type below to inspect the exact JSON schema delivered through /ws/v2/stream.

{
  "type": "LIQ_CASCADE",
  "symbol": "BTCUSDT",
  "side": "Sell",
  "price": 78500.0,
  "impact": 1250000.0,
  "timestamp": 1741684800.12,
  "verdict_state": "Deleveraging",
  "impact_pct": 0.2,
  "cvd_1m": -127010000.0,
  "cvd_5m": -123420000.0,
  "cvd_15m": -125980000.0,
  "oi_delta_pct": 0.06,
  "funding_rate": 0.000087,
  "liq_count": 5
}

Unified Payload Field Reference

Field Type Source Description
type string All Anomaly identifier: LIQ_CASCADE, VOL_SPIKE, WALL_SWEEP, OI_EXPLOSION, BTC_DECOUPLING, WHALE_LIQ_DANGER, WHALE_POSITION_INFLOW.
source string Sonar Execution provenance: HYPERLIQUID_ONCHAIN or Binance Futures.
symbol string All Normalized market pair identifier (e.g. BTCUSDT, ETHUSDT, SOLUSDT).
side string All Position direction / market pressure: Long / Short or Buy / Sell.
impact float All Notional dollar magnitude: liquidation USD volume, whale position USD, or inflow delta.
wallet string Sonar Hyperliquid L1 0x hexadecimal address of the tracked mega-whale.
hypurr_url string Sonar Direct verifiable explorer link to the whale on HypurrScan.io.
liq_price float Sonar Exact on-chain liquidation threshold calculated by Hyperliquid L1 margin engine.
dist_pct float Sonar Percentage distance from current mark price to whale's liquidation price.
hl_skew object Sonar Aggregate Hyperliquid L1 order flow positioning ratio (long_pct vs short_pct).
cvd_1m/5m/15m float Core Cumulative Volume Delta across 1, 5, and 15-minute rolling windows.
oi_delta_pct float Core 5-minute Open Interest change percentage (validates aggressive buildup vs exit).

Institutional REST Snapshot Endpoints

In addition to continuous WebSocket streaming, pull cached market snapshots on startup:

Method Endpoint Description Parameters
GET / Service overview, engine versioning, supported event taxonomies, and links. None
GET /health / /api/v2/status Sub-millisecond health telemetry, active WebSocket subscribers, and Redis status. None
GET /api/v2/events/recent Fetch the last 1–100 market events cached across both Binance and Hyperliquid. limit=20 (1–100)
GET /api/v2/events/sonar Fetch the latest Hyperliquid on-chain mega-whale anomalies (Danger & Inflow). limit=10 (1–50)

Dual-Engine Algorithmic Client Snippets

Connect your bot in less than 30 lines of code. Handles both Binance and Hyperliquid events.

import asyncio
import json
import websockets

API_KEY = "YOUR_API_KEY"
WS_URL = f"wss://sigma-liq.fun/ws/v2/stream?api_key={API_KEY}"

async def listen_institutional_stream():
    async with websockets.connect(WS_URL) as ws:
        # 1. Receive handshake with engine specifications
        handshake = await ws.recv()
        print(f"⚡ Authenticated: {handshake}")

        # 2. Real-time dual-engine anomaly event loop
        while True:
            raw = await ws.recv()
            event = json.loads(raw)
            ev_type = event.get("type")

            # Branch A: Hyperliquid L1 Whale Sonar Danger Alert
            if ev_type == "WHALE_LIQ_DANGER":
                symbol = event["symbol"]
                dist = event["dist_pct"]
                pos = event["position_usd"]
                print(f"🐋 [WHALE SONAR] {symbol} {event['side']} Whale ${pos:,.0f} | ONLY {dist:.1f}% to LIQ @ ${event['liq_price']}")

            # Branch B: Binance Futures Liquidation Cascade
            elif ev_type == "LIQ_CASCADE":
                print(f"🔥 [BINANCE CASCADE] {event['symbol']} {event['side']} Liq Vol: ${event['impact']:,.0f}")

if __name__ == "__main__":
    asyncio.run(listen_institutional_stream())

Frequently Asked Technical Questions

How does Whale Sonar track Hyperliquid L1 on-chain whales?

Whale Sonar connects directly to Hyperliquid L1 nodes and monitors the top-30 largest perpetual positions by margin and notional size. When mark price approaches within 5.0% of a whale's liquidation price, or when a whale expands their position by ≥ $1,000,000, a structured on-chain event is broadcasted with an explorer link to verify on HypurrScan.

What is the execution latency of the WebSocket stream?

Internal processing latency from event calculation to client WebSocket push is under 5 milliseconds. Events bypass relational database queries and are distributed directly from in-memory Redis Pub/Sub.

Which markets and cryptocurrencies are covered?

The feed monitors 100 USDT-margined perpetual futures on Binance 24/7 alongside the top-30 mega-whales on Hyperliquid L1 (including BTC, ETH, SOL, SUI, AVAX, DOGE, and other major liquid perps).

How is authentication handled, and are there rate limits?

Pass your token in the WebSocket connection URL (?api_key=...) or via the X-API-Key header. Because connections are persistent bi-directional WebSockets, rate limit bans (HTTP 429) are completely eliminated during high-volatility cascades.

Get Your Institutional API Key

Full dual-engine WebSocket stream access with sub-millisecond delivery is included with VIP access. Connect your trading terminal today.

Get VIP Access via Tribute Join Free Telegram Channel