1. Executive Summary
DoubleLiquid preserves the official Hyperliquid API surface while routing compatible HTTP and WebSocket traffic through DoubleZero-powered network paths. Traders change the base API URL, keep the same request bodies, signatures, response formats, SDKs, and operational patterns, and receive lower and more predictable latency to Hyperliquid infrastructure.
Asia routing is Tokyo-first because Hyperliquid servers are understood to be in Tokyo. DoubleLiquid should avoid Hong Kong or Singapore detours unless route telemetry proves those paths produce a lower end-to-end Tokyo result for a specific client region.
2. Alignment With DoubleZero Grants
Routes real latency-sensitive trading API traffic over DoubleZero paths.
Adoption requires a URL change rather than a bot, SDK, or signing rewrite.
Focuses on application-layer routing, observability, and trader-facing evidence.
3. Problem
Hyperliquid traders compete on milliseconds, but new low-latency infrastructure often creates integration risk. If a faster path requires new SDKs, payload schemas, signing behavior, or trading workflows, serious teams postpone adoption. DoubleLiquid keeps the API contract identical and moves the improvement into the network path.
4. Product Definition
- Same official Hyperliquid HTTP paths, including
/infoand/exchange. - Same WebSocket subscription and post-message behavior as the official endpoint.
- Same JSON bodies, signatures, nonce semantics, status codes, and response payloads.
- No custody, no private key handling, and no order mutation.
https://api.doubleliquid.xyz
wss://api.doubleliquid.xyz/ws
5. Technical Approach
DoubleLiquid is a thin compatibility layer with a strong emphasis on transparency, parity, and operational reliability. HTTP requests and signed exchange actions are forwarded unchanged. The WebSocket layer preserves subscriptions, acknowledgements, market data updates, user channels, and supported post-message order flow.
US East and US West ingress route to Tokyo egress. Asia traffic is anchored on Tokyo by default, with egress adjacent to Hyperliquid infrastructure.
Because DoubleZero currently supports Solana out of the box, the Hyperliquid route will be enabled in close coordination with the DoubleZero team before production traffic is directed through it.
6. Security and Trust Model
- Users keep their own wallets, API wallets, and signing infrastructure.
- DoubleLiquid never receives private keys.
/exchangeactions remain user-signed before they enter DoubleLiquid.- Request and response bodies are not modified.
- Sensitive request logging is disabled by default.
7. Builder-Code Monetization
Builder codes are not part of the grant-funded launch. Any future monetization must be
explicit, opt-in, and client-side because signed /exchange payloads cannot
be mutated invisibly without breaking the drop-in API promise.
8. Milestones and Success Criteria
| Milestone | Timeline | Success Criteria | Tranche |
|---|---|---|---|
| Production architecture and route plan | Weeks 1-2 | Tokyo-centered route plan finalized | $6,000 (10%) |
| HTTP API parity development | Weeks 3-4 | Official SDK uses DoubleLiquid URL for core calls | $12,000 (20%) |
| WebSocket parity development | Weeks 5-6 | Subscriptions and reconnect behavior match official expectations | $9,000 (15%) |
| DoubleZero Hyperliquid route deployment | Weeks 7-8 | Hyperliquid-specific Tokyo route enabled with DoubleZero team input and deployed with p50 improvement on at least two target routes | $12,000 (20%) |
| Production SLO dashboard and user onboarding | Weeks 9-10 | Daily route telemetry and 3-5 early users onboarded | $12,000 (20%) |
| Hardening, handoff, and grant report | Weeks 11-12 | Final route-level p50/p90/p99 and readiness report | $9,000 (15%) |
9. Budget
| Category | Amount | Notes |
|---|---|---|
| Core API engineering | $24,000 | HTTP proxy, WebSocket proxy, compatibility coverage, deployment automation |
| DoubleZero Hyperliquid route deployment | $12,000 | Coordination with the DoubleZero team to enable Hyperliquid routing, US-to-Tokyo route setup, Tokyo Asia routing, failover path, deployment runbook |
| Production telemetry and SLO dashboard | $8,000 | Measurement agents, route-status dashboard, p50/p90/p99 reporting, baseline comparisons |
| Security and reliability hardening | $7,000 | Logging controls, failover behavior, load profile, abuse controls, review time |
| Production onboarding and grant closeout | $9,000 | SDK examples, onboarding sessions, issue triage, final route report, maintenance plan |
The request is deliberately mid-sized: enough to cover concrete development and deployment work, but scoped as a milestone subsidy rather than full-time compensation.
10. Risks and Mitigations
| Risk | Mitigation |
|---|---|
| DoubleZero path does not beat the official path on every route | Publish route-level data, focus traffic on routes where DoubleZero wins, and keep official-path failover. |
| API parity breaks trading clients | Build against official docs and SDK behavior, preserve payloads without mutation, and maintain golden response coverage. |
| Added proxy hop increases tail latency | Track p50/p90/p99 continuously, route only where DoubleZero wins, expose status, and fail open to the official endpoint. |
| Sensitive trading data in logs | Disable payload logging by default and store only timings, status codes, route IDs, and hashed request IDs. |
11. Maintenance Plan
After the grant period, DoubleLiquid will remain usable as production infrastructure with compatibility monitoring against official Hyperliquid docs and SDK examples, route performance monitoring by region, a public status and SLO page, documented failover to the official API, and optional paid or builder-code sustainability only after explicit user consent and committee feedback.