2026-06-22

Electrum Wallet Tor Integration — Route Bitcoin Transactions Through Tor

BY GH0STWIRE // Guides
Electrum Wallet Tor Integration — Route Bitcoin Transactions Through Tor

Last year, a researcher I work with watched his entire transaction history get linked back to his home IP because he forgot to flip one toggle in Electrum before broadcasting a payment to a darknet vendor. The coins were clean, the wallet was solid, but the network connection leaked everything. Routing Electrum through Tor closes that leak, and it takes about four minutes to set up properly.

What This Setup Actually DoesElectrum is a lightweight Bitcoin client that talks to remote servers over the internet. By default, those servers see your IP address, the addresses in your wallet, and every balance query you make. When you route Electrum through Tor, the server only sees a Tor exit node IP. Your real network identity stays separated from your Bitcoin activity.This matters for anyone transacting with markets like Nexus, Torzon, or DarkMatter, where vendor payouts or refund addresses can quietly fingerprint users over time. Tor integration does not make Bitcoin anonymous — the blockchain is still public — but it removes the network-level link between your wallet and your physical location.PrerequisitesBefore touching Electrum settings, you need a working Tor daemon on your machine. The Tor Browser Bundle ships with one, but it only runs while the browser is open. For a persistent setup, install the standalone Tor service.

  • Tor Browser 13.5 or newer, or the standalone Tor Expert Bundle 0.4.8.x
  • Electrum 4.5.0 or newer — older versions have known proxy bugs
  • A clean wallet file, ideally created on an offline machine or Tails session
  • Optional: Tails OS 6.x if you want the entire stack running from RAM
  • Do not skip the version check. Electrum 4.4.x had a bug where the proxy settings silently reverted after restart, which is exactly the kind of mistake that exposes people.Step 1: Start the Tor ServiceIf you are using the Tor Browser, launch it once and let it connect. The SOCKS5 proxy is then available at 127.0.0.1:9150. If you installed the standalone Tor service, it listens on 127.0.0.1:9050 by default. Confirm the port is open before moving on — a common mistake is assuming Tor is running when the browser crashed silently.On Linux, run systemctl status tor and look for the active state. On macOS with Homebrew, brew services list shows the same info. On Windows, check the Tor Expert Bundle console window for the “Bootstrapped 100%” line.Step 2: Configure Electrum’s ProxyOpen Electrum and go to Tools → Preferences → Network. Under Proxy, select “SOCKS5”, enter 127.0.0.1 as the host, and use 9050 for the standalone service or 9150 if you are routing through the Tor Browser. Check the box labeled “Use proxy at startup” so the setting survives a restart.There is a second setting people miss: under the Server tab, make sure “Select server automatically” is enabled and that “Onion” servers appear in the list. Electrum will then prefer .onion Electrum servers, which means the entire connection — server queries, transaction broadcasting, header downloads — stays inside the Tor network. If you only set the proxy but connect to a clearnet server like electrum.blockstream.info, you are still leaking metadata to whoever runs that server.Step 3: Verify the ConnectionClose Electrum and reopen it to confirm the proxy persisted. Then go to Tools → Network Monitor and watch the connection log. You should see connections to hostnames ending in .onion. If you see clearnet hostnames, the proxy is not actually being used.A quick sanity check: open the Tor Browser, load check.torproject.org, and confirm it reports you as using Tor. Then in Electrum, view your receive address and check the network tab — the server should be a .onion address. If Electrum shows an error like “cannot connect to proxy”, the Tor service probably crashed. Restart it and try again.Common Issues and TroubleshootingThe most frequent problem is Electrum falling back to a clearnet server after a Tor restart. This happens when the proxy checkbox is unchecked or when the port number is wrong. Another issue is firewall software blocking outbound connections on port 9050 — Windows Defender and Little Snitch on macOS both do this by default.If transactions refuse to broadcast, the issue is usually a stale server list. Go to Tools → Preferences → Network and click “Cancel” then re-enable automatic server selection. Electrum will pull a fresh list of .onion servers from a hardcoded source.Additional Security RecommendationsTor protects your network layer, not your wallet file. Encrypt your wallet with a strong passphrase, store the seed on paper or metal in a separate physical location, and consider running Electrum inside Tails if you are handling large amounts. Pairing Tor-routed Electrum with Feather Wallet for Monero gives you a layered setup where the Bitcoin side is private at the network level and the XMR side is private at the protocol level.Finally, never reuse addresses. Tor hides where you connect from, but every reused address builds a public graph on-chain that no proxy can erase.

    Submit Response

    REQUIRED FIELDS ARE MARKED *

    Tor List – Darknet Markets

    LAST REVIEWED: 2026-09-17
    Research Disclaimer

    This directory is provided strictly for informational and research purposes. DarkScope does not host, operate, or maintain any marketplace. No links on this site lead to illegal content. All .onion addresses are presented as redacted reference data for academic and journalistic research into darknet infrastructure patterns.

    Notice

    This archive provides no direct links to illegal services, does not facilitate any transactions of any kind, and does not enable access to listed platforms. Address tokens are placeholders for verification reference only. Users are solely responsible for their own actions and jurisdictional compliance.

    TOR LIST - DARKNET MARKETS // VERIFICATION ARCHIVE // 2026