Hyperliquid Wallet: Complete Setup Guide for OneKey Users

Jan 26, 2026

What you’ll set up (and why it matters)

When trading via a self-custodial interface, your “account” is ultimately controlled by your wallet’s private key. A hardware wallet adds an extra safety layer because:

Your private key stays isolated on the device
You verify critical actions (approvals, deposits, transfers) on-screen
You reduce the risk of malware-based signing

Prerequisites checklist

Hardware and software

A OneKey hardware device (updated to the latest firmware)
OneKey companion app / browser extension (whichever you normally use to connect to dApps)
A modern browser (for desktop) or a mobile phone (for WalletConnect-style connections)

Funds you’ll need (common case)

ETH on Arbitrum One for gas
USDC on Arbitrum One for collateral deposits (most common onboarding path)

The official onboarding flow highlights that deposits commonly start from Arbitrum because the native bridge connects Arbitrum and the protocol’s core chain. (Official “How to start trading” onboarding) (hyperliquid.gitbook.io)

Step 1: Initialize your OneKey device safely

Create a new wallet or import an existing seed

Create a new wallet if you want a clean trading identity
Import only if you fully trust the environment where your seed has ever existed

Lock down the basics

Set a strong PIN
Back up your recovery phrase offline (never in cloud notes or screenshots)
Consider enabling a passphrase for an extra protection layer (advanced, but highly effective)

Update before connecting

Firmware and app updates often include security fixes and dApp compatibility improvements. Update before you connect to any trading interface.

Step 2: Prepare your network(s)

Add Arbitrum One (for bridging and collateral)

Most users fund from Arbitrum. If you need to bridge from Ethereum to Arbitrum, follow the official Arbitrum user quickstart. (Arbitrum user quickstart) (docs.arbitrum.io)

Also note that Arbitrum’s official bridge URL has been updated to the portal domain. (Arbitrum portal bridge notice) (portal.arbitrum.io)

(Optional) Add HyperEVM (for EVM apps)

If you plan to use EVM-based apps in the ecosystem, you can add the network directly. The official docs list these parameters: (How to use the HyperEVM) (hyperliquid.gitbook.io)

Network Name: Hyperliquid
Chain ID: 999
RPC URL: https://rpc.hyperliquid.xyz/evm
Currency Symbol: HYPE
Explorer (optional): https://hyperevmscan.io/

You can also add it via Chainlist: Chainlist: Chain 999. (hyperliquid.gitbook.io)

Step 3: Fund your wallet on Arbitrum One

Option A: Withdraw directly to Arbitrum One

If your exchange supports withdrawals to Arbitrum One, this is often the simplest route:

Withdraw ETH (Arbitrum One) for gas
Withdraw USDC (Arbitrum One) for deposits

Option B: Bridge from Ethereum to Arbitrum One

Use Arbitrum’s official bridge flow:

Bridge ETH first (so you can pay gas on Arbitrum)
Then bridge USDC (or swap into the right USDC flavor on Arbitrum, depending on what you receive)

Reference: Arbitrum bridge quickstart. (docs.arbitrum.io)

Step 4: Connect your wallet to the official trading interface

Verify you are on the real site

Use bookmarks
Double-check the domain before connecting/signing

Open the official interface here: Trading page. (hyperliquid.gitbook.io)

Choose the connection method that matches your setup

Desktop: connect via your OneKey-supported browser wallet flow
Mobile: use a WalletConnect-style connection from the site, then confirm on your OneKey device

If you’re curious how WalletConnect coordinates signatures across clients, see: WalletConnect v2 specs (Sync Protocol). (specs.walletconnect.com)

Step 5: Deposit collateral (USDC from Arbitrum)

From the trading interface:

Click Deposit
Select USDC
Approve (token allowance) and confirm on your OneKey screen
Deposit and confirm again

Important constraints from the official bridge documentation:

The bridge between the core chain and Arbitrum has a minimum deposit amount (5 USDC); smaller deposits can be lost. (Bridge2 API docs) (hyperliquid.gitbook.io)
Deposits are generally credited quickly once processed (often within about a minute). (Bridge2 API docs) (hyperliquid.gitbook.io)

Security note: approvals are the “real” risk surface

A deposit typically requires an ERC-20 approval first. Treat approvals as seriously as transfers:

Approve only what you need (avoid “infinite approve” if you’re cautious)
Revoke old approvals periodically with tools like Revoke.cash

Step 6: Withdraw back to Arbitrum (when you’re done)

On the trading interface:

Click Withdraw
Choose withdraw-to-Arbitrum
Confirm any required signatures on your OneKey device

The official bridge overview explains the validator-signed withdrawal flow and notes a 1 USDC withdrawal gas fee to cover Arbitrum-side costs. (Bridge overview) (hyperliquid.gitbook.io)

Optional: Use HyperEVM without introducing avoidable risk

If you add HyperEVM, keep these practical points in mind:

Get gas token (HYPE) only when needed

HyperEVM uses HYPE as gas. Plan small test transactions first, especially when interacting with new contracts. (How to use the HyperEVM) (hyperliquid.gitbook.io)

Understand why gas can spike

The docs also explain that early throughput is intentionally constrained and gas follows an Ethereum-style base fee mechanism. (Background: EIP-1559) (hyperliquid.gitbook.io)

Troubleshooting (fast checks)

“Deposit doesn’t show up”

Confirm you’re on Arbitrum One
Confirm you have enough ETH on Arbitrum for gas (approval + deposit)
Check the transaction status on an explorer
Ensure you did not send less than the documented minimum deposit (5 USDC). (Bridge2 API docs) (hyperliquid.gitbook.io)

“The site asks me to re-connect repeatedly”

Refresh the page
Try a clean browser profile
Re-pair WalletConnect sessions and remove old sessions you no longer use

Security and trust: what to verify before you size up

Prefer audited core infrastructure (but still practice defense-in-depth)

The bridge has been audited by Zellic, and you can review the report directly. (Zellic audit reports: Hyperliquid) (reports.zellic.io)

Audits reduce risk, but they don’t eliminate phishing, approval abuse, or user-side errors—so hardware confirmation + URL verification remain essential.

When a OneKey device is especially worth using (practical reasons)

If you plan to trade actively, you’ll sign approvals, deposits, transfers, and occasional configuration transactions. A OneKey hardware wallet is most valuable here because it:

Keeps keys off your everyday computer/phone
Forces you to confirm the action on a separate, trusted screen
Makes “silent signing” malware much harder to pull off

If you want, tell me whether you’re using desktop or mobile and whether you plan to use HyperEVM, and I can tailor the exact click-by-click flow (including which confirmations you should expect on-device) to your setup.