Use WalletConnect in the BitBoxApp to connect your BitBox’s Ethereum account to Hyperliquid. This guide takes you through the connection and shows how to review a subsequent request to sign Hyperliquid’s terms on your BitBox. It does not cover deposits, trading, withdrawals or every permission Hyperliquid may request.

Before you connect

• You need a BitBox with the Multi edition that has already been set up.
• Make sure the BitBoxApp and your BitBox firmware are up to date.
• Have the BitBox for your intended Ethereum account available for signing.
• For iPhone or iPad, you need a compatible BitBox Nova. For desktop or Android, have a compatible USB connection available.

Never enter recovery words, an optional passphrase or private keys into Hyperliquid or a connection form. A hardware wallet protects its keys, but an authorized signature can still have consequences. Only proceed with requests you understand.

Connect to Hyperliquid with WalletConnect

First, get a connection link from Hyperliquid and paste it into the BitBoxApp. Alternatively, scan a QR code displayed on another device. The screenshots show Hyperliquid in a desktop browser and the BitBoxApp on iPad. For shared network support and troubleshooting, see the WalletConnect guide.

1. Open app.hyperliquid.xyz in your browser and check the domain.
2. Select Connect in the upper-right corner, then select WalletConnect in the wallet list.

3. In the WalletConnect dialog, select Copy link beneath the QR code. If you prefer to scan, leave the QR code open on the other device. Use the link or code generated for your current session, not the website address or one from a guide. Keep the pairing link and QR code private.
4. Open the BitBoxApp and select the Ethereum account you want to connect to Hyperliquid.
5. On that account’s page, select Wallet Connect.
6. On the WalletConnect page, select New connection to open the connection form.
7. Paste the copied link into Enter URI address of dapp. To scan instead, select the QR-code icon in that field and scan the current code on the Hyperliquid website.
8. If you pasted a link, select Connect. Scanning submits the code directly. The BitBoxApp displays a new connection request.
9. Review the account address, DApp name and website in the request. Check that the address belongs to the account you selected and that the request identifies Hyperliquid and https://app.hyperliquid.xyz. A displayed name or logo alone does not prove authenticity. Select Reject if anything is unexpected.

10. If the details match and you want to connect, select Approve Connection.
11. Wait for Dapp successfully connected. You can continue on the dapp website. Select Done and return to Hyperliquid.

The connection is complete when the BitBoxApp reports success and Hyperliquid appears in the WalletConnect session list. Connecting has not deposited funds or completed a trade. Hyperliquid may next show its terms or request a signature; review that as a separate decision.

Review the optional terms-signature request

Follow this section if Hyperliquid asks you to accept its terms and you choose to agree. In the captured example, this generates a typed-data signature request: a structured message with fields to review in the app and on your BitBox.

The values below describe that example. Later versions of Hyperliquid, other requests and other DApps can show different fields or confirmation sequences. A request resembling this example is not automatically safe.

1. Read the terms on the Hyperliquid website. If you choose to agree, select Accept. Return to the BitBoxApp when the WalletConnect request appears.
2. Check Account, Chain and Dapp. They must match the account and action you intended. This example shows Arbitrum One and Hyperliquid.
3. Review Type and Data to understand the request. In the example, the type is Sign typed data. The data includes type: acceptTerms and primaryType: Hyperliquid:AcceptTerms, identifying it as a terms-acceptance request. Check the complete data; these names alone do not establish that it is trustworthy.

4. Select Continue only if you intend to proceed with that request.
5. If the BitBoxApp asks you to connect your BitBox, connect and unlock the device for the account shown in the request.
6. On the BitBox display, check the full Ethereum signing address against your intended account, then review the message type.
7. Review every domain and message field presented on the BitBox. Compare each complete value with the corresponding field in the BitBoxApp and check that it matches the action you intended on Hyperliquid.

In this terms-signature example, the device’s domain review has four fields:

The BitBox then presents hyperliquidChain, with the value Mainnet, and time. Compare the time value with the request too; it changes between requests. Review every field your BitBox presents, including any beyond this example.

8. After reviewing every screen, confirm Sign data on the BitBox by holding both sides when prompted. Do this only if you intend to authorize the message you just reviewed.
9. Wait for Request successfully signed in the BitBoxApp, then return to Hyperliquid to check its result.

This message confirms that the request was signed, not that a deposit or trade completed. A message signature is returned to the DApp and is not necessarily an on-chain transaction. Hyperliquid can subsequently show Establish Connection, a deposit dialog or other requests. Review each new action independently: a gas-free signature can still grant permissions, and later actions may not require another hardware confirmation.

Disconnect Hyperliquid

1. In the BitBoxApp, open the Ethereum account you used for the connection.
2. Select Wallet Connect on the account page.
3. Find Hyperliquid in the session list and select Remove.
4. Check that Hyperliquid’s entry disappears from the list.

This disconnects the WalletConnect session. It does not reverse signed actions, recover transferred funds or revoke permissions already granted through signatures or transactions. Use Hyperliquid’s official guidance if you need to review those permissions.

If your screen differs or a request fails

If Hyperliquid presents a different request, do not approve it just to follow this guide. Check the actual request against your intended action and every field on the BitBox display. Cancel if you cannot establish what you would authorize.

For a rejected pairing link or unsupported network or method, follow WalletConnect connection and request troubleshooting. A successful connection or terms signature does not establish that every Hyperliquid feature is compatible.

If a BitBox error persists, contact BitBox Support with your BitBox model, app and firmware versions, operating system, network, request type and exact non-sensitive error. Never include wallet secrets, backup files, pairing links or pairing QR codes.