Pairing lets your BitBox and a wallet application establish an authenticated, encrypted connection. When a pairing code appears, compare it on both screens before confirming on the BitBox.

You do not always need to pair with the BitBoxApp before using another wallet application. Sparrow 2.1.0 and later can pair directly with your BitBox. Initial device setup and firmware updates are separate tasks that you still perform through the BitBoxApp.

What does pairing protect?

Pairing helps protect communication between your BitBox and the application from interception or alteration. Comparing the codes checks that the application and the device are establishing the same encrypted connection.

It does not create a new wallet or transfer your funds. The communication keys used for pairing are separate from your wallet's recovery words.

Never enter wallet secrets to pair

You never need to enter recovery words, a wallet backup, or a private key into wallet software to pair your BitBox.

 

A successful pairing does not make every request from the application safe. Continue to verify receiving addresses and transaction details on your BitBox before using an address or approving a transaction.

Do I need the BitBoxApp before using Sparrow?

If your BitBox has not been set up, use the BitBoxApp to complete its initial setup and protect its backup first. Keep the BitBoxApp installed so you can update your BitBox firmware.

Once the device is set up, Sparrow 2.1.0 and later handle pairing themselves. You do not need to return to the BitBoxApp solely to establish a pairing for Sparrow. Follow Connect your BitBox to Sparrow Wallet for the USB connection procedure.

Wallet applications that support direct pairing

The following applications can handle pairing with an already set-up BitBox without requiring prior pairing through the BitBoxApp:

  • Sparrow Wallet (version 2.1.0 and later)
  • Electrum
  • Liana
  • MyEtherWallet
  • Rabby
  • AdaLite

These are examples rather than a complete compatibility list. Supported assets and connection options depend on the application and your BitBox model and edition. Use an up-to-date version of the application and follow its BitBox connection instructions; the pairing screens and confirmation steps can differ.

How to compare a pairing code

These instructions concern the code shown when connecting your BitBox to wallet software over USB. Bluetooth pairing on an iPhone or iPad is a separate connection flow.

  1. When the wallet application and your BitBox display a pairing code, compare every group of characters on the two screens.
  2. Only if the complete codes match, confirm the pairing on your BitBox. Follow any further confirmation prompt in the application. In Sparrow, the pairing dialog waits for your confirmation on the BitBox and then closes automatically.

If the codes do not match

If the codes differ, reject the pairing on the BitBox and stop. Check that you installed the application from its official source. If the mismatch persists, contact BitBox Support before proceeding. Do not reset the device or restore your wallet to resolve a pairing mismatch.

 

Why am I asked to pair again?

The device and application remember an approved pairing. A different application, another computer, or loss of an application's pairing configuration can require a new comparison, even if you have used the same BitBox before.

Compare the codes currently shown by the application and device with each other. You do not need to keep an old pairing code or enter it as a password.

If the application cannot connect

Close the BitBoxApp and other wallet applications before connecting through the application you want to use. If Sparrow cannot detect your BitBox, unplug it and reconnect it. On Linux, BitBoxApp 4.47.0 and earlier had an exclusive-access issue that could require reconnecting the device; update the BitBoxApp if you still use an affected version.

If the problem continues, contact BitBox Support with your operating system, wallet application and version, BitBox model, firmware version if available, and the exact error text. Never send recovery words, backup files, private keys, passwords, or an optional passphrase.