NautilusTrader
Integrations

Hyperliquid

Hyperliquid is a decentralized perpetual futures and spot exchange built on the Hyperliquid L1, a purpose-built blockchain optimized for trading. HyperCore provides a fully on-chain order book and matching engine. This integration supports live market data ingest and order execution on Hyperliquid.

Overview

This adapter is implemented in Rust with Python bindings. It provides direct integration with Hyperliquid's REST and WebSocket APIs without requiring external client libraries.

The Hyperliquid adapter includes multiple components:

  • HyperliquidHttpClient: Low-level HTTP API connectivity.
  • HyperliquidWebSocketClient: Low-level WebSocket API connectivity.
  • HyperliquidInstrumentProvider: Instrument parsing and loading functionality.
  • HyperliquidDataClient: Market data feed manager.
  • HyperliquidExecutionClient: Account management and trade execution gateway.
  • HyperliquidLiveDataClientFactory: Factory for Hyperliquid data clients (used by the trading node builder).
  • HyperliquidLiveExecClientFactory: Factory for Hyperliquid execution clients (used by the trading node builder).

Most users will define a configuration for a live trading node (as shown below) and won't need to work directly with these lower-level components.

Examples

You can find live example scripts here.

Revoking builder code approval

Previous versions of NautilusTrader required users to approve a builder code fee before trading. This is no longer required. If you previously approved the builder fee and wish to revoke it, you can run the revoke script.

The script reads your private key from environment variables (HYPERLIQUID_PK or HYPERLIQUID_TESTNET_PK).

python nautilus_trader/adapters/hyperliquid/scripts/builder_fee_revoke.py

Testnet:

HYPERLIQUID_TESTNET=true python nautilus_trader/adapters/hyperliquid/scripts/builder_fee_revoke.py

Alternatively, from Rust:

cargo run --bin hyperliquid-builder-fee-revoke

Testnet setup

Hyperliquid provides a testnet environment for testing strategies with mock funds.

Mainnet account required. Hyperliquid's testnet faucet only works for wallets that have previously deposited on mainnet. You must fund a mainnet account first before you can obtain testnet USDC.

Getting testnet funds

To receive testnet USDC, you must first have deposited on mainnet using the same wallet address:

  1. Visit the Hyperliquid mainnet portal and make a deposit with your wallet.
  2. Visit the testnet faucet using the same wallet.
  3. Claim 1,000 mock USDC from the faucet.

Email wallet users: Email login generates different addresses for mainnet vs testnet. To use the faucet, export your email wallet from mainnet, import it into MetaMask or Rabby, then connect the extension to testnet.

Creating a testnet account

  1. Visit the Hyperliquid testnet portal.
  2. Connect your wallet (MetaMask, WalletConnect, or email).
  3. The testnet automatically creates an account for your wallet address.

Exporting your private key

To use your testnet account with NautilusTrader, you need to export your wallet's private key:

MetaMask:

  1. Click the three dots menu next to your account.
  2. Select "Account details".
  3. Click "Show private key".
  4. Enter your password and copy the private key.

Never share your private keys. Store private keys securely using environment variables; never commit them to version control.

Setting environment variables

Set your testnet credentials as environment variables:

export HYPERLIQUID_TESTNET_PK="your_private_key_here"
# Optional: for vault trading
export HYPERLIQUID_TESTNET_VAULT="vault_address_here"

The adapter automatically loads these when testnet=True in the configuration.

Product support

Hyperliquid offers linear perpetual futures and native spot markets.

Product TypeData FeedTradingNotes
Perpetual FuturesUSDC-settled linear perps.
SpotNative spot markets.

Perpetual futures on Hyperliquid are settled in USDC. Spot markets are standard currency pairs.

Symbology

Hyperliquid uses a specific symbol format for instruments:

Perpetual futures

Format: {Base}-USD-PERP

Examples:

  • BTC-USD-PERP - Bitcoin perpetual futures
  • ETH-USD-PERP - Ethereum perpetual futures
  • SOL-USD-PERP - Solana perpetual futures

To subscribe in your strategy:

InstrumentId.from_str("BTC-USD-PERP.HYPERLIQUID")
InstrumentId.from_str("ETH-USD-PERP.HYPERLIQUID")

Spot markets

Format: {Base}-{Quote}-SPOT

Examples:

  • PURR-USDC-SPOT - PURR/USDC spot pair
  • HYPE-USDC-SPOT - HYPE/USDC spot pair

To subscribe in your strategy:

InstrumentId.from_str("PURR-USDC-SPOT.HYPERLIQUID")

Spot instruments may include vault tokens (prefixed with vntls:). These are automatically handled by the instrument provider.

Instrument provider

The instrument provider supports filtering when loading instruments via InstrumentProviderConfig(filters=...):

Filter keyTypeDescription
market_types (or kinds)list[str]"perp" or "spot".
baseslist[str]Base currency codes, e.g. ["BTC", "ETH"].
quoteslist[str]Quote currency codes, e.g. ["USDC"].
symbolslist[str]Full symbols, e.g. ["BTC-USD-PERP"].

Example loading only perpetual instruments:

instrument_provider=InstrumentProviderConfig(
    load_all=True,
    filters={"market_types": ["perp"]},
)

Data subscriptions

The adapter supports the following data subscriptions:

Data typeSubscriptionHistoricalNautilus typeNotes
Trade ticks-TradeTickVia WebSocket trades channel.
Quote ticks-QuoteTickBest bid/offer from WebSocket.
Order book deltas-OrderBookDeltaL2 depth. Each message is a full snapshot.
BarsBarSee supported intervals below.
Mark prices-MarkPriceUpdatePerpetual mark price ticks.
Index prices-IndexPriceUpdateUnderlying index reference prices.
Funding rates-FundingRatePerpetual funding rate updates.

Historical quote tick and trade tick requests are not yet supported by this adapter.

Supported bar intervals

ResolutionHyperliquid candle
1-MINUTE1m
3-MINUTE3m
5-MINUTE5m
15-MINUTE15m
30-MINUTE30m
1-HOUR1h
2-HOUR2h
4-HOUR4h
8-HOUR8h
12-HOUR12h
1-DAY1d
3-DAY3d
1-WEEK1w
1-MONTH1M

Orders capability

Hyperliquid supports a full set of order types and execution options.

Order types

Order TypePerpetualsSpotNotes
MARKETIOC limit at 0.5% slippage from best BBO.
LIMIT
STOP_MARKETStop loss orders.
STOP_LIMITStop loss with limit execution.
MARKET_IF_TOUCHEDTake profit at market.
LIMIT_IF_TOUCHEDTake profit with limit execution.

Conditional orders (stop and if-touched) are implemented using Hyperliquid's native trigger order functionality with automatic TP/SL mode detection. All trigger orders are evaluated against the mark price.

Market orders require cached quote data. The adapter uses the best ask (for buys) or best bid (for sells) with 0.5% slippage. Prices are rounded to 5 significant figures, which is a Hyperliquid API requirement for all limit prices. Ensure you subscribe to quotes for any instrument you intend to trade with market orders.

STOP_MARKET and MARKET_IF_TOUCHED orders do not carry a limit price. The adapter derives one from the trigger price with 0.5% slippage, rounds to 5 significant figures, and clamps to the instrument's price precision (ceiling for buys, floor for sells). This guarantees Hyperliquid's limit_px >= trigger_px (buys) / limit_px <= trigger_px (sells) constraint.

Price normalization is enabled by default. Hyperliquid enforces a maximum of 5 significant figures on all order prices. This is a dynamic constraint that depends on the price magnitude and cannot be fully encoded in the static instrument price precision. For example, if ETH is trading at $2,600 (4 integer digits), only 1 decimal place is allowed despite the instrument having price_precision=2.

By default, the adapter normalizes all outgoing limit and trigger prices to 5 significant figures to prevent order rejections. This means your submitted prices may shift slightly. To disable this and take full control of price formatting, set normalize_prices=False in your HyperliquidExecClientConfig.

If you disable normalization, you can apply the same rounding in your strategy:

from decimal import Decimal, ROUND_DOWN

def round_to_sig_figs(price: Decimal, sig_figs: int = 5) -> Decimal:
    if price == 0:
        return Decimal(0)
    shift = sig_figs - int(price.adjusted()) - 1
    if shift <= 0:
        factor = Decimal(10) ** (-shift)
        return (price / factor).to_integral_value() * factor
    return round(price, shift)

Time in force

Time in forcePerpetualsSpotNotes
GTCGood Till Canceled.
IOCImmediate or Cancel.
FOK--Not supported.
GTD--Not supported.

Execution instructions

InstructionPerpetualsSpotNotes
post_onlyEquivalent to ALO time in force.
reduce_onlyClose-only orders.

Post-only orders that would immediately match are rejected by Hyperliquid. The adapter detects this and generates an OrderRejected event. Post-only orders are routed through Hyperliquid's ALO (Add-Liquidity-Only) lane.

Order operations

OperationPerpetualsSpotNotes
Submit orderSingle order submission.
Submit order listBatch order submission (single API call).
Modify orderRequires venue order ID.
Cancel orderCancel by client order ID.
Cancel all ordersIterates cached open orders by instrument/side.
Batch cancelIterates provided cancel list.

Cancel all and batch cancel issue individual cancel requests per order.

Orders placed outside NautilusTrader (e.g. via the Hyperliquid web UI or another client) are detected and tracked as external orders. They appear in order status reports and position reconciliation.

Order books

Order books are maintained via L2 WebSocket subscription. Each message delivers a full-depth snapshot (clear + rebuild), not incremental deltas.

There is a limitation of one order book per instrument per trader instance.

Account and position management

The adapter uses cross-margin mode and reports account state with USDC balances and margin usage. On connect, the execution client performs a full reconciliation of orders, fills, and positions against Hyperliquid's clearinghouse state. This ensures the local cache is consistent even after restarts or disconnections.

Leverage is managed directly through the Hyperliquid web UI or API, not through the adapter. Set your desired leverage per instrument on Hyperliquid before trading.

Connection management

The adapter automatically reconnects on WebSocket disconnection using exponential backoff (starting at 250ms, up to 5s). On reconnect, all active subscriptions are resubscribed automatically, and order book snapshots are rebuilt. No manual intervention is required.

A heartbeat ping is sent every 30 seconds to keep the connection alive (Hyperliquid closes idle connections after 60 seconds).

API credentials

There are two options for supplying your credentials to the Hyperliquid clients. Either pass the corresponding values to the configuration objects, or set the following environment variables:

For Hyperliquid mainnet clients, you can set:

  • HYPERLIQUID_PK
  • HYPERLIQUID_VAULT (optional, for vault trading)

For Hyperliquid testnet clients, you can set:

  • HYPERLIQUID_TESTNET_PK
  • HYPERLIQUID_TESTNET_VAULT (optional, for vault trading)

We recommend using environment variables to manage your credentials.

Vault trading

Hyperliquid supports vault trading, where a wallet operates on behalf of a vault (sub-account). Orders are signed with the wallet's private key but include the vault address in the signature payload.

To trade via a vault, set the vault_address in your execution client config (or set the HYPERLIQUID_VAULT / HYPERLIQUID_TESTNET_VAULT environment variable).

When vault trading is enabled, WebSocket subscriptions for order and fill updates automatically use the vault address instead of the wallet address. This is required to receive the vault's order and fill events.

Rate limiting

The adapter implements a token bucket rate limiter for Hyperliquid's REST API with a capacity of 1200 weight per minute. HTTP info requests are automatically retried with exponential backoff (full jitter) on rate limit (429) and server error (5xx) responses.

Configuration

Data client configuration options

OptionDefaultDescription
base_url_wsNoneOverride for the WebSocket base URL.
testnetFalseConnect to the Hyperliquid testnet when True.
http_timeout_secs10Timeout (seconds) applied to REST calls.
http_proxy_urlNoneOptional HTTP proxy URL.
ws_proxy_urlNoneReserved; WebSocket proxy not yet implemented.

Execution client configuration options

OptionDefaultDescription
private_keyNoneEVM private key; loaded from HYPERLIQUID_PK or HYPERLIQUID_TESTNET_PK when omitted.
vault_addressNoneVault address; loaded from HYPERLIQUID_VAULT or HYPERLIQUID_TESTNET_VAULT if omitted.
base_url_wsNoneOverride for the WebSocket base URL.
testnetFalseConnect to the Hyperliquid testnet when True.
max_retriesNoneMaximum retry attempts for submit, cancel, or modify order requests.
retry_delay_initial_msNoneInitial delay (milliseconds) between retries.
retry_delay_max_msNoneMaximum delay (milliseconds) between retries.
http_timeout_secs10Timeout (seconds) applied to REST calls.
normalize_pricesTrueNormalize order prices to 5 significant figures before submission.
http_proxy_urlNoneOptional HTTP proxy URL.
ws_proxy_urlNoneReserved; WebSocket proxy not yet implemented.

Configuration example

from nautilus_trader.adapters.hyperliquid import HYPERLIQUID
from nautilus_trader.adapters.hyperliquid import HyperliquidDataClientConfig
from nautilus_trader.adapters.hyperliquid import HyperliquidExecClientConfig
from nautilus_trader.config import InstrumentProviderConfig
from nautilus_trader.config import TradingNodeConfig

config = TradingNodeConfig(
    data_clients={
        HYPERLIQUID: HyperliquidDataClientConfig(
            instrument_provider=InstrumentProviderConfig(load_all=True),
            testnet=True,  # Use testnet
        ),
    },
    exec_clients={
        HYPERLIQUID: HyperliquidExecClientConfig(
            private_key=None,  # Loads from HYPERLIQUID_TESTNET_PK env var
            vault_address=None,  # Optional: loads from HYPERLIQUID_TESTNET_VAULT
            instrument_provider=InstrumentProviderConfig(load_all=True),
            testnet=True,  # Use testnet
            normalize_prices=True,  # Rounds prices to 5 significant figures
        ),
    },
)

When testnet=True, the adapter automatically uses testnet environment variables (HYPERLIQUID_TESTNET_PK and HYPERLIQUID_TESTNET_VAULT) instead of mainnet variables.

Then, create a TradingNode and add the client factories:

from nautilus_trader.adapters.hyperliquid import HYPERLIQUID
from nautilus_trader.adapters.hyperliquid import HyperliquidLiveDataClientFactory
from nautilus_trader.adapters.hyperliquid import HyperliquidLiveExecClientFactory
from nautilus_trader.live.node import TradingNode

# Instantiate the live trading node with a configuration
node = TradingNode(config=config)

# Register the client factories with the node
node.add_data_client_factory(HYPERLIQUID, HyperliquidLiveDataClientFactory)
node.add_exec_client_factory(HYPERLIQUID, HyperliquidLiveExecClientFactory)

# Finally build the node
node.build()

Contributing

For additional features or to contribute to the Hyperliquid adapter, please see our contributing guide.

On this page