Connect your BitBox to Sparrow Wallet over USB to view your Bitcoin account and prepare transactions that you approve on the BitBox. Sparrow imports the account’s public information; your private keys stay on the device. Connecting does not create a new BitBox wallet or move your bitcoin.

This guide covers the first Native Segwit account in a single-signature wallet. If you want to use another account or address type, its settings must match the account you already use.

Before you begin

  • Use an already set-up BitBox with its backup stored securely. Keep the BitBoxApp installed for device management and firmware updates; complete any available update before continuing.
  • Install the current stable Sparrow release from the official Sparrow download page and follow its download-verification instructions.
  • If this is your first time using Sparrow, complete its welcome screens and server setup. A server connection is needed to load transaction history and balances. A public server can learn information about your wallet’s addresses and transactions; using your own node or a trusted private server gives you more control over that disclosure.
  • Close the BitBoxApp and other wallet applications before connecting through Sparrow. Have a USB connection that supports data, including any required adapter.

You do not need to pair with the BitBoxApp first: Sparrow 2.1.0 and later handle their own pairing. Initial device setup and firmware maintenance remain separate tasks.

Keep wallet secrets on your BitBox

Never enter recovery words, a wallet backup, your BitBox device password, or an optional wallet passphrase into Sparrow. Use the connected hardware-wallet option below. A request to import recovery words is not part of this procedure.

 

1. Create the Sparrow wallet file

Sparrow calls its local account record a wallet. Creating this file gives Sparrow a place to store the public account information and labels; it does not generate a new wallet on your BitBox.

  1. In Sparrow, choose File → New Wallet, or select New Wallet on the start screen.
Sparrow start screen with New Wallet.
  1. Enter a name you will recognize, such as My BitBox, then select Create Wallet. Sparrow opens the wallet’s Settings screen.
Sparrow Wallet Name dialog and Create Wallet button.
  1. For the account covered here, check that Policy Type is Single Signature and Script Type is Native Segwit (P2WPKH). Under Keystores, select Connected Hardware Wallet. Do not select New or Imported Software Wallet.
Sparrow wallet settings with the hardware-wallet connection option.

2. Connect, unlock, and pair your BitBox

  1. Connect your BitBox to the computer by USB. In Sparrow’s hardware-wallet window, select Scan… to search for the device.
Sparrow hardware-wallet scan window.
  1. When prompted, unlock the BitBox by entering its device password on the device. If you see a warning about remaining password attempts and do not know the password, stop rather than continuing to guess.
  2. If the optional passphrase feature is enabled, enter the exact passphrase for the intended wallet on the BitBox and verify the complete entry on its display before confirming. To open the standard wallet, leave the passphrase empty. A different passphrase opens a different wallet without an incorrect-passphrase error. See using an optional passphrase if you are unsure which wallet you need.
  3. If a pairing code appears in Sparrow and on the BitBox, compare every group of characters on both displays. Only if the complete codes match, confirm on the BitBox. Sparrow’s pairing dialog then closes automatically.
Sparrow pairing code to compare with the code displayed on the BitBox.

If the codes differ, reject the pairing and stop. If Sparrow reports that the device failed its authenticity check, stop before using the wallet. Contact BitBox Support for either unresolved warning; do not reset the device or restore a backup to try to fix it.

3. Import and check the intended account

A keystore is Sparrow’s record of the keys for a wallet. For this hardware-wallet connection, it contains public information that lets Sparrow find the account’s addresses and transactions, without receiving its private keys.

  1. Once Sparrow shows the unlocked BitBox, open the arrow beside Import Keystore. For the first Native Segwit account, choose Default Account #0, then select Import Keystore. Sparrow returns to the wallet’s Settings screen.
BitBox account import in Sparrow.
  1. Check the imported settings. For this example, Policy Type is Single Signature, Script Type is Native Segwit (P2WPKH), and Derivation is m/84'/0'/0'. The keystore type identifies the connected BitBox.
Sparrow single-signature wallet settings.

The derivation path identifies which account’s public keys Sparrow imported; the descriptor describes how its addresses are constructed. Leave the imported values intact when they match the account you intended. Another account index or address type needs different settings. If you are unsure, stop and ask Support rather than changing these fields by trial and error.

4. Protect the wallet file and verify completion

  1. Select Apply in the wallet’s Settings screen. When Sparrow asks for a wallet-file password, use a separate password to protect the information stored on your computer. Enter it in both password fields and confirm the dialog. You can leave the fields empty and select No Password, but the file will not have that password protection.
Optional password for the Sparrow wallet file.

This password protects the Sparrow wallet file and its private financial information. It is different from the BitBox device password and the optional passphrase that selects a BitBox wallet. It does not change either of them or replace your BitBox backup.

Sparrow wallet after importing the BitBox account.
  1. Open Transactions in Sparrow’s left sidebar. With Sparrow connected to its server, allow the account history to load. If you have used this account before, check that the expected transactions and balance appear. An unused account can correctly have no history.

The account import is complete when Sparrow has saved the connected BitBox keystore with the intended account settings. For an account you already use, also check its history after synchronization before treating the displayed balance as complete.

Before sharing a receiving address, open Receive in Sparrow and select Display Address with your BitBox connected and unlocked. Compare the full address in Sparrow with the address on the BitBox. If they differ, stop and do not use the address. Continue to verify transaction details on the BitBox whenever you sign a payment.


If something does not work

Sparrow cannot find the BitBox

Close other wallet applications, unplug and reconnect the BitBox, and select Scan… again. Check the device display for an unlock prompt and try another data-capable USB cable, adapter, or port. On Linux, BitBoxApp 4.47.0 and earlier had an exclusive-access issue that could require unplugging and reconnecting the device; update the BitBoxApp if you still use an affected version.

If Sparrow reports incompatible firmware, update it through the BitBoxApp, then close that app before retrying. Do not reset the BitBox or import recovery words into Sparrow.

The pairing codes do not match

Reject the pairing on the BitBox. Check that Sparrow came from its official download page. If the mismatch persists, contact Support before continuing.

The expected balance or history is missing

First check that Sparrow is connected to its server and has finished loading the account. Then check whether you imported the intended account index and address type. If you use an optional passphrase, an empty entry or any different spelling opens another wallet. Reconnect the BitBox and enter the intended passphrase exactly on the device before importing that account.

An empty account alone does not mean your bitcoin is lost. Do not reset the device, recreate your BitBox wallet, or enter recovery words into software to investigate.

You need help continuing

Contact BitBox Support with your computer operating system, Sparrow version, BitBox model and firmware version if available, the step where you are stuck, and the exact error text. Never send recovery words, backup files, private keys, passwords, or an optional passphrase. Avoid screenshots containing public keys or other private financial information.