Official API baseline
Route telemetry compares DoubleLiquid latency against the official path from the same client regions.
Production API routing for latency-sensitive teams
DoubleLiquid
A production-oriented Hyperliquid API endpoint routed through DoubleZero, built for lower order-flow and market-data latency with the same client integration surface.
from
https://api.hyperliquid.xyz
to
https://api.doubleliquid.xyz
Scope
Official HTTP and WebSocket parity
Trust model
No custody, no keys, no order rewrites
Route focus
Tokyo edge path for Hyperliquid traffic
API parity
Same Hyperliquid contract. Production route control.
DoubleLiquid mirrors the official request and response surface for existing bots, market makers, dashboards, and SDK wrappers. Signed exchange actions remain signed by the user before they enter the proxy and are forwarded without order mutation.
const apiUrl = "https://api.doubleliquid.xyz";
const wsUrl = "wss://api.doubleliquid.xyz/ws";
POST /info // forwarded unchanged
POST /exchange // signed payload preserved
WS /ws // subscriptions preservedProduction telemetry
Latency claims tied to live route-level evidence.
DoubleLiquid is framed around production SLOs: p50, p90, p99, jitter, timeout rate, WebSocket acknowledgement time, and official API baseline comparisons from the same client regions.
No HK or Singapore detour
Asian traffic is anchored on Tokyo because Hyperliquid infrastructure is there; other Asian clients should ride the shortest DoubleZero path into Tokyo.
Hyperliquid-oriented path
Keep egress close to Hyperliquid's Tokyo servers to avoid unnecessary regional hops.
Grant fit
Infrastructure that makes DoubleZero directly usable by traders.
DoubleLiquid is scoped as a focused infrastructure grant: ship the adapter, operate the Tokyo path, onboard production users, and publish route-level SLO evidence. It complements DoubleZero core development with an application-layer proof point.
01Production architecture and route plan
02HTTP and WebSocket parity launch
03DoubleZero route deployment
04Public SLO dashboard and production report
Operating principles
Designed for traders who already trust their own stack.
No private keys
Wallets and API wallets stay with the client. DoubleLiquid only sees signed requests.
No hidden fees
Builder-code monetization is future, optional, and user-signed. It stays outside the launch path.
No vague speed claims
Targets are useful only when backed by public route-level measurements.
Failover first
Traffic can fall back to the official API if a DoubleZero route underperforms.