Configure the BitBoxApp to route its backend connections through a local Tor proxy and reduce the network-level metadata exposed to the services it contacts.

You can use the Tor proxy with the BitBoxApp's default servers or with your own Bitcoin full node. A personal full node is not required.

Before you begin

This workflow covers the desktop BitBoxApp on Windows, macOS, and Linux. Before changing the proxy settings:

• Install the latest version of the BitBoxApp.
• Install Tor Browser from the official Tor Project website or use an existing Tor background service.
• Start Tor and connect it to the Tor network.

Keep Tor running whenever the BitBoxApp uses the proxy. If you use Tor Browser as the proxy, keep Tor Browser open and connected.

Choose the Tor proxy address

Use the SOCKS proxy address that matches how Tor runs on your computer:

These are the usual local proxy addresses. If you configured Tor to use a different SOCKS port, use that address instead.

Enable the Tor proxy in the BitBoxApp

1. Open the BitBoxApp.
2. Select Settings in the sidebar.
3. Open Advanced settings.
4. Select Enable Tor proxy.

5. Enable the proxy in the Set proxy address window.
6. Enter the SOCKS proxy address that matches your Tor setup:
   • Tor Browser normally uses 127.0.0.1:9150.
   • A Tor background service normally uses 127.0.0.1:9050.

7. Select Set proxy address.

8. Close the BitBoxApp completely so the new proxy configuration can be applied.
9. Open the BitBoxApp again.

The BitBoxApp now routes its backend connections through the configured Tor proxy without displaying connection errors. Keep Tor running while using the BitBoxApp.

How Tor changes BitBoxApp privacy

The Tor proxy routes BitBoxApp network traffic through the Tor network before it reaches the Bitcoin services the BitBoxApp communicates with. This helps prevent those services from seeing your normal public IP address and reduces network-level metadata exposure.

The Tor proxy does not change which Bitcoin backend the BitBoxApp uses. Unless you configure a different backend, the BitBoxApp continues to use its default servers through Tor.

To use Bitcoin infrastructure you control, follow the steps to connect the BitBoxApp to your own Bitcoin full node. You can combine that setup with Tor when your Bitcoin full node is reachable through a Tor onion address.

For a broader explanation of network communication and privacy controls, learn what data is shared when using the BitBoxApp.

The BitBoxApp shows connection refused

An error such as Lost connection, trying to reconnect followed by connection refused means the BitBoxApp cannot reach the configured local Tor proxy.

1. Make sure Tor Browser is open and connected, or confirm that the Tor background service is running.
2. Open Settings in the BitBoxApp.
3. Open Advanced settings.
4. Select Enable Tor proxy.
5. Check the complete proxy address:
   • Use 127.0.0.1:9150 for the usual Tor Browser setup.
   • Use 127.0.0.1:9050 for the usual Tor background-service setup.
6. Save the proxy address.
7. Close the BitBoxApp completely.
8. Open the BitBoxApp again.
9. If the configured proxy address is correct but the connection still fails, verify that your firewall or security software is not preventing local connections to the Tor proxy.

If you no longer want to use Tor, disable the Tor proxy and restart the BitBoxApp.

Frequently asked questions

Do I need my own Bitcoin full node to use Tor with the BitBoxApp?

No. The BitBoxApp can route connections to its default servers through Tor. Connecting to your own Bitcoin full node is a separate privacy control that changes which Bitcoin infrastructure the BitBoxApp uses.

Can I enable the Tor proxy without Tor running?

No. The BitBoxApp requires a running Tor proxy at the configured address. If Tor Browser or the Tor service is not running, the BitBoxApp cannot establish backend connections and displays a connection error.

Must Tor Browser remain open while I use the BitBoxApp?

Yes, if Tor Browser provides the proxy. Tor Browser must remain open and connected while the BitBoxApp uses 127.0.0.1:9150. A Tor background service can provide the proxy continuously instead.

Does using Tor make every BitBoxApp interaction anonymous?

No. Tor reduces network-level metadata exposure for connections routed through the configured proxy. It does not replace a personal full node or remove information that you deliberately provide to external services.