BitBoxBridge is a background application that connects your BitBox to supported web wallets and browser-based services on your computer. You need it only when the connection method used by your chosen wallet or service requires it. You do not need BitBoxBridge for normal use of the BitBoxApp or for AOPP requests handled by the BitBoxApp.
The wallet integration matters as well as the browser. For example, Rabby's BitBox connection requires BitBoxBridge even in Chrome, while MyEtherWallet's documented direct connection in Chrome works without it.
Do I need BitBoxBridge for my connection?
| Connection method | Is BitBoxBridge needed? |
|---|---|
| Normal use of the BitBoxApp | No. The BitBoxApp communicates with your BitBox without Bridge. |
| An AOPP request handled by the BitBoxApp | No. The request opens the BitBoxApp directly. |
| MyEtherWallet's legacy interface using the direct Chrome connection | No. Follow the MyEtherWallet connection guide for that method. |
| Rabby's BitBox integration | Yes, including when using Chrome or Brave. Follow the Rabby connection guide. |
| AdaLite | No in Chrome. Other browsers require BitBoxBridge. Follow the AdaLite guide for the connection steps. |
| NuFi | No in Chrome. Other browsers require BitBoxBridge. Follow the NuFi connection guide. |
| Another wallet or website | Check its BitBox connection instructions. The wallet must support the chosen connection method; installing Bridge alone does not make an unsupported integration work. |
A browser's ability to connect directly to USB devices does not mean that every wallet uses that feature. Similarly, installing Bridge does not guarantee that a particular wallet works in Firefox, Safari or another browser. Use the browser and connection method specified in the wallet's guide.
Why AOPP does not need BitBoxBridge
The Address Ownership Proof Protocol (AOPP) lets a service request proof that you control a Bitcoin address. When you open an AOPP request with the BitBoxApp, the app handles the request and asks you to review and confirm the proof on your BitBox. The website does not need a direct hardware-wallet connection through Bridge for this process.
Pocket Bitcoin and Coinfinity are examples of services with documented AOPP integrations. This is not a complete provider list, and the available process depends on the service. For AOPP guidance and links to service-specific instructions, see how to prove control of a Bitcoin address with BitBox.
What Bridge does—and what you still need to check
When an integration uses Bridge, the wallet in your browser communicates with the background application on your computer, which passes requests to your BitBox. Your private keys remain on the BitBox; Bridge does not require you to import your wallet backup.
Bridge may ask whether a website is allowed to connect to your BitBox. Approve only a connection you deliberately started, and check that the requesting website is the one you intended to use. Reject an unexpected or unfamiliar request. Some connections proceed without a separate Bridge permission prompt.
Allowing a website to connect is separate from comparing a pairing code or approving a transaction. If a pairing code appears, compare the complete code in the wallet application with the one on your BitBox and confirm only if they match. Continue to check transaction details on the BitBox before approving them; a working connection does not establish that a website or its requests are trustworthy.
Keep wallet secrets out of websites
Never enter recovery words, a private key, your BitBox device password or an optional passphrase into a website, and never upload a wallet backup. Enter device secrets only on your BitBox. If a website asks for them, stop and close it.
Install Bridge or check an existing installation
If your connection requires Bridge, download it from the official BitBox download page and follow the BitBoxBridge installation guide. After installation, it normally runs in the background. Close the BitBoxApp and other wallet applications using the device before connecting through your chosen web wallet.
To check whether Bridge is reachable on your computer, open http://127.0.0.1:8178/ in your browser. You can also use http://localhost:8178/. A Bridge status page shows the installed version and available connection endpoints. The version may differ from examples in other guides.
A reachable status page confirms that the local Bridge service responds. It does not confirm that your BitBox is detected, that the website has permission, that pairing is complete or that your wallet connection works. If the status page does not load, or the wallet still cannot connect, follow BitBoxBridge troubleshooting before reinstalling or changing security settings.