Connecting the BitBoxApp through Tor is a great way to increase your privacy while managing your crypto assets. This guide shows you how to configure the BitBoxApp to use your existing Tor setup on your computer.


Before you start

Make sure Tor is already installed and running on your computer. This could be the Tor Browser application or the Tor background service.

 

Set up Tor in the BitBoxApp

Follow these steps to route the BitBoxApp's network connections through your local Tor proxy.

  1. Open the BitBoxApp on your computer (Windows, macOS, or Linux).
  2. Click Settings in the lower-left corner of the sidebar.
  3. In the settings menu, click Advanced settings.
  4. Find and click the row labeled “Enable Tor proxy”. A new window will open.
  1. In the “Set proxy address” window, click the toggle to enable the feature.
  1. Enter the following details:
    1. Proxy Address: 127.0.0.1 (this is the standard address for a service running on your own computer)
    2. Proxy Port:
      1. Use 9150 if you are running the Tor Browser.
      2. Use 9050 if you are running the Tor background service (daemon).
  2. Click the confirmation button to save the settings.

Important: You must completely close and restart the BitBoxApp. The proxy settings are only applied when the app starts.

 

How BitBoxApp uses Tor

Once configured, all of the BitBoxApp's backend network communication is routed through your local Tor proxy. This hides your real IP address from the services the app connects to, including:

  • Shift Crypto's default Electrum servers for Bitcoin and Litecoin.
  • The BitBoxApp update checker.
  • Cryptocurrency exchange rate providers.
  • The Etherscan.io API for Ethereum and ERC20 token information.

This configuration uses Tor with the BitBoxApp's default servers. You do not need to enter any .onion addresses in the Connect your own full node section for this to work.


Troubleshooting

  • Symptom: You see an error message that says “Lost connection, trying to reconnect…” followed by text like connect: connection refused.
  • Fix: This error means the BitBoxApp cannot connect to the Tor proxy. Ensure that Tor (e.g., Tor Browser) is running on your computer and that you have entered the correct port number (9150 or 9050) in the BitBoxApp settings. If you don't want to use Tor, you can disable the proxy setting to fix the connection.

Frequently Asked Questions (FAQ)

Do I have to restart the BitBoxApp after enabling Tor?

Yes. It is critical that you completely close and reopen the BitBoxApp after enabling or disabling the Tor proxy setting. The BitBoxApp only applies network settings on startup.

What is the difference between port 9150 and 9050?

The Tor Browser application typically uses port 9150 for its SOCKS proxy. The Tor background service (often called the Tor daemon) usually uses port 9050. You must use the port that matches your specific Tor setup.

Does this connect me to my own full node over a .onion address?

No. This setting routes the BitBoxApp's standard connections through the Tor network. It is separate from the feature to connect to your own full node, which has its own settings for .onion addresses.