Hyperliquid Wallet Setup: Complete OneKey Configuration Guide

Jan 26, 2026

Why this setup matters in 2026

Onchain trading has moved fast over the last year: high-performance L1 venues are becoming the default for active traders, while stablecoin rails are shifting toward native crosschain transfer standards (for example, Circle’s CCTP and its newer CCTP V2 announced on March 11, 2025). This pushes one practical question to the top of every user’s checklist: how do you trade frequently without turning private-key management into the weakest link? See Circle CCTP and the CCTP V2 announcement.

This guide walks through a secure, repeatable configuration for using a OneKey wallet with Hyperliquid, covering connection, deposits, withdrawals, and optional HyperEVM network settings.

Before you start: a quick architecture overview

HyperCore vs HyperEVM (what you’re actually connecting to)

Hyperliquid’s stack is commonly described in two parts:

HyperCore: the onchain trading engine (spot and perps order books).
HyperEVM: an EVM execution environment secured by the same consensus, intended for smart contracts and EVM-style dApp interactions.

If you’re new, you’ll usually start by connecting an EVM address to the trading interface and funding your account. The official onboarding flow is documented here: How to start trading.

Step 1: Prepare your OneKey device (security-first baseline)

1) Create a dedicated “trading” account on your hardware wallet

For operational safety, separate funds by intent:

Cold long-term storage account (rarely connects to dApps)
Active trading account (limited balance, used for signatures and approvals)

This reduces blast radius if you ever approve a malicious contract or sign something you didn’t fully understand.

2) Verify your backup and local security settings

Checklist:

Seed backup is offline and verified (no photos, no cloud notes).
Device PIN is set and not reused elsewhere.
Optional passphrase is enabled if that matches your security model.
Firmware and OneKey client software are up to date.

3) Use least-privilege by default

When a dApp asks for approvals:

Start with a small test deposit.
Avoid unlimited allowances unless you actively need them.
Periodically revoke old approvals using a reputable token-approval tool like Revoke.cash.

Step 2: Connect to the trading interface (and understand the first signature)

1) Open the official site and verify the domain

Always type the URL manually or use a trusted bookmark. Phishing is still the #1 cause of “hardware wallet drained” stories.

Reference the official onboarding entry point: How to start trading.

2) Connect using a hardware-wallet compatible flow

Most users will connect through either:

A browser wallet interface that can route signatures to your OneKey device, or
A WalletConnect-compatible connection from a mobile wallet that controls OneKey keys

3) “Enable Trading” = a signature step (not a gas spend)

After connecting, you’ll be prompted to Enable Trading, which (per the official onboarding guide) requires signing a gas-less action. Treat this like any other signature:

Confirm the domain is correct.
Read the message contents (especially if it’s typed data).
If anything looks unusual, reject and investigate.

If you want a deeper technical explanation of typed structured signing, review EIP-712.

Step 3: Fund your account safely (deposits)

Option A (most common): Deposit USDC via Arbitrum

The native bridge flow uses USDC on Arbitrum, and you’ll need a small amount of ETH on Arbitrum for gas.

Official bridge details (including minimum deposit and timing): Bridge2 documentation
Official onboarding walkthrough (UI steps): How to start trading
If a deposit is missing because you sent the wrong asset: Deposit / transfer issues (USDC via Arbitrum)

Practical checklist (recommended):

Bridge / move funds to Arbitrum using an official route such as the Arbitrum Bridge.
Confirm you hold USDC on Arbitrum and enough ETH for gas.
Deposit a small amount first (operational test), then scale up.

Option B: Multi-chain deposits (when applicable)

The onboarding guide also describes depositing other assets (for example BTC, ETH, or SOL) depending on the account type and supported rails at the time. If you go this route, follow the official deposit instructions carefully to avoid sending unsupported assets to the wrong network: How to start trading.

Step 4: Withdraw correctly (and know what you’re signing)

Withdrawals are typically designed to be user-signature based, with protocol validators handling the onchain fulfillment on the destination side.

User-facing withdrawal steps: How to start trading
Developer-grade details (fees, expected finalization time, signing fields): Exchange endpoint (withdraw3)

Safety notes:

Always verify the destination address on your OneKey screen (where applicable).
If you are asked to sign typed data, read it carefully and confirm it matches the intended withdrawal.

Step 5 (optional): Add HyperEVM network settings to your wallet

If you plan to interact with EVM applications in the ecosystem, you may want to add HyperEVM as a custom network.

Official parameters (including chain IDs and RPC endpoints): HyperEVM documentation.

Network: HyperEVM (Mainnet)
RPC URL: https://rpc.hyperliquid.xyz/evm
Chain ID: 999
Gas token: HYPE

Getting gas (HYPE) onto HyperEVM

The official HyperEVM docs explain how HYPE is used for gas and how transfers between components work, including the address used for moving HYPE from HyperCore to HyperEVM: HyperEVM documentation.

Operational tip: do a small test transfer first, then proceed with larger amounts once you confirm balances and UI behavior.

Step 6 (advanced): Use an Agent / API wallet for automation (without risking withdrawals)

If you run bots or want programmatic trading, you may encounter the concept of an Agent wallet (sometimes called an API wallet). The idea is simple: keep your “master” key on OneKey, and delegate limited trading permission to an agent key.

How agent approval is represented at the API level: Exchange endpoint (approveAgent)
A practical overview of creating an agent wallet via the UI: Agent wallet creation notes

Key security principle: an agent key should be treated like a hot key (because it often lives on a server). Use strict opsec: IP restrictions where possible, minimal balances, and clear key rotation.

Common issues and fixes (quick troubleshooting)

“Deposit not showing up”

Most common causes:

You deposited an unsupported asset or used the wrong network.
You sent less than the minimum deposit threshold stated in the bridge docs.

Start with the official troubleshooting entry: Deposited via Arbitrum network (USDC).

“Signature / Enable Trading fails”

Try:

Refreshing the page and reconnecting your wallet session.
Ensuring the OneKey device is unlocked and ready to sign.
Checking whether your wallet UI requires explicit permission for typed-data signing (EIP-712): EIP-712.

“I’m worried I approved too much”

Revoke old approvals and reduce allowances:

Revoke.cash

When it makes sense to use OneKey for this workflow

If you actively trade but still want hardware-backed key custody, OneKey fits best when you:

Keep your master key offline while signing critical actions on-device
Separate cold storage from a dedicated trading account
Use limited allowances and periodic approval cleanup
Optionally delegate automation to an agent key while keeping withdrawals protected by your hardware wallet flow

For a fast-moving onchain trading stack, the real win is not just “having a hardware wallet”, but using it with an operational model that matches modern risks: phishing, signature ambiguity, approval sprawl, and crosschain complexity.