On this page
Hyperliquid HyperEVM DEX
This is separate from Hyperliquid's main perp / HIP-3 / HIP-4 surfaces.
It targets HyperEVM (chain ID 999), where Permit2 + ERC-20 routers
power AMM-style swaps.
Endpoints
| Artery | Returns |
|---|---|
GET /v1/hyperliquid/dex/chain-info | chain ID, RPC URL, native HYPE token |
GET /v1/hyperliquid/dex/tokens | curated HyperEVM token list |
Planned additions:
GET /v1/hyperliquid/dex/quote → quote + Permit2 typed data + router calldata
POST /v1/hyperliquid/dex/swap → user signs Permit2 + tx, Artery relays to RPC
GET /v1/hyperliquid/dex/status/:tx → poll confirmation
Why Permit2 (not approveAgent)?
HyperEVM is a separate EVM chain. approveAgent is HL Core only — it delegates trading
authority on the order-book exchange but does nothing for ERC-20 swaps. HyperEVM uses standard
ERC-20 + Uniswap-style Permit2.
Architecture: routing through HyperSwap V3
Artery's HL DEX adapter targets HyperSwap V3 directly:
mermaidsequenceDiagram
Client->>Artery: GET /quote (from, to, amount)
Artery->>HyperSwap: read quoter / pool fees
Artery-->>Client: { quote, permit2: {domain,types,message}, transaction }
Client->>Wallet: sign Permit2 + tx
Client->>Artery: POST /swap (sigs)
Artery->>HyperEVM RPC: eth_sendRawTransaction
Artery-->>Client: { txHash }
Client->>Artery: GET /status/:tx (poll)Aggregator integration (LiquidSwap, OKX DEX) is on the roadmap — when OKX adds chain 999 support we'll add it as a fallback route.
Slippage + deadline
Default 0.5% (50 bps) max slippage and 30-minute quote expiry. Override
via ?slippage_bps= and the deadline encoded in the quote payload.
MEV protection — Artery does not route through Flashbots / private mempools. For large swaps, configure your client wallet to use a private RPC or wait for the planned MEV-Protect integration.
Bridge between HyperCore and HyperEVM
Artery currently assumes you already have HyperEVM balances. The Core ↔ EVM bridge
(per-token system addresses 0x20...<tokenIndex>, HYPE special-cased to
0x2222...2222) is planned.