A Bitcoin user running a full node has already decided that verifying the chain locally matters more than accepting third-party assertions about transaction validity. That commitment to independence becomes incomplete, however, if wallet queries still route through servers controlled by other parties. When the wallet asks “has this address received funds?” or “what is the current fee rate?”, the server observing that question learns something about the user’s financial interests, even if the transaction itself remains encrypted or mixed. A self-hosted Electrum server eliminates that surveillance point by making the wallet and the blockchain query infrastructure part of the same system under the user’s complete control.
Wasabi Wallet’s architecture already reflects privacy-first design principles: CoinJoin mixing, open-source code, hardware wallet support, and no custodial intermediaries. But privacy infrastructure is only as strong as its weakest information leak. For users who have already accepted the operational overhead of running a full node, connecting Wasabi to a personal Electrum server represents the logical next step. This is not a configuration for casual users. It requires familiarity with command-line tools, networking concepts, and the patience to troubleshoot when something does not connect as expected. For those users, however, the payoff is substantial: complete elimination of queries to third-party blockchain services and full visibility into exactly what information leaves the local network.

Why a personal Electrum server matters for privacy
Default Wasabi setup uses coordinator servers operated by the Wasabi development team to handle CoinJoin coordination and to respond to wallet balance queries. While those coordinators do not control user funds and cannot prevent mixing transactions from being broadcast, they do observe which addresses are queried and from which network contexts. Over time, patterns of balance checks, mix rounds, and transaction timing can be correlated with external network data or user metadata. A personal Electrum server eliminates that observation point entirely: the server is part of your network infrastructure, responding only to your wallet, under your control.
The distinction is significant because privacy is not simply a feature toggle in software. It is a system of controls across multiple layers. Wasabi’s CoinJoin mechanism protects the transaction on the blockchain itself by mixing multiple payments into a single transaction where the input-to-output mapping becomes ambiguous. That protection does nothing to prevent an observer from seeing which addresses you query or which balance updates trigger wallet activity. A self-hosted Electrum server addresses that earlier layer: the wallet makes no external network requests, and no third party learns what addresses you are interested in.
This approach also eliminates dependency on the Wasabi coordinator’s availability or policies. If the coordinator experiences downtime or changes rules around which transactions can be mixed, a user relying on personal infrastructure has full control. The trade-off is operational: running an Electrum server requires a separate machine, disk space, bandwidth, and responsibility for keeping both the Bitcoin node and the Electrum server in sync. For a user who already operates a full node, the incremental effort is manageable. For a casual user, it is probably not worth the complexity.
The second important distinction is coordinator-free versus chain-query privacy. Eliminating coordinator observations does not eliminate blockchain analysis of the mixed transaction itself, nor does it protect against network-level timing attacks if an observer can correlate when the transaction is broadcast with other external events. A personal Electrum server does not make you anonymous to the blockchain; it makes you invisible to the services querying it on your behalf.
Prerequisites: Bitcoin node and Electrum server infrastructure
Before connecting Wasabi to a personal Electrum server, you need two running processes: a full Bitcoin node that maintains a copy of the entire blockchain and validates new transactions according to consensus rules, and an Electrum server that indexes that blockchain and responds to wallet queries. Bitcoin Core is the reference implementation and the most widely deployed choice. It requires approximately 600–700 GB of disk space (and growing), 2–4 GB of RAM, and sufficient bandwidth to sync with the peer-to-peer network. The initial sync can take 12–48 hours depending on hardware and network speed.
For the Electrum server component, electrs (Electrum Rust Server) is the most popular choice among power users because it is lightweight, fast, and can run on commodity hardware. It builds an index on top of the Bitcoin node’s data, enabling fast queries for balances and transaction history. Installation requires Rust (a programming language), the Bitcoin node directory accessible to the Electrum server process, and typically a few gigabytes of additional disk space for the index. An alternative is ElectrumX, a Python implementation that is more memory-intensive but often already packaged in Linux distributions.
Both options require that the Bitcoin node is fully synced and the Electrum server is indexed before connecting Wasabi. A partially synced node or incomplete index will cause wallet balance queries to return incorrect results, leading to confusion or missed transactions. The safest approach is to verify sync status on the Bitcoin node using the RPC interface, confirm that the Electrum server reports a healthy block height matching the network tip, and then test a simple balance query from a separate device before introducing Wasabi into the flow.
Hardware requirements deserve emphasis. A Raspberry Pi 4 with 8 GB RAM and a USB SSD can run both Bitcoin Core and electrs, though full node syncing takes longer and disk writes are more intensive. A used desktop with 16 GB RAM and a 2 TB SSD is more comfortable. The machine should have an uninterruptible power supply or at least automatic shutdown on power loss to prevent database corruption. If the machine is running 24/7, electricity cost becomes part of the hidden infrastructure expense; budgeting for that is part of the realistic decision to self-host.
Installing and configuring electrs on your local network
Assuming a Bitcoin node is already running and synced, installing electrs begins with installing Rust and then building electrs from source. On Debian-based Linux systems, the sequence typically involves installing build dependencies, cloning the electrs repository, compiling with Cargo (Rust’s package manager), and specifying the Bitcoin node’s data directory and the listening port for the Electrum server. The official electrs documentation includes specific commands; copying them without understanding what they do is a common source of failure because paths or permissions may differ on your system.
Configuration requires pointing electrs to the Bitcoin node’s directory (typically ~/.bitcoin on Linux) and choosing the network interface and port the Electrum server will listen on. For a machine on a local home network, binding to 127.0.0.1 (localhost only) adds another layer of security by preventing external access, though it means Wasabi must run on the same machine or you must use a local network address. More advanced setups use firewalling, Tor hidden services, or SSH tunneling to expose the Electrum server to trusted devices while maintaining access control. The key principle is that exposing an Electrum server to the public internet creates a new attack surface: anyone can query it, learn which addresses are active, and potentially use traffic analysis to de-anonymize the owner.
Once electrs is running, it begins building its index. This process reads every block from the Bitcoin node and creates a database mapping addresses to their transactions. On a fast SSD, indexing the full chain takes 4–12 hours. During this time, the Electrum server will respond to queries, but queries may return incomplete results if not all blocks have been indexed yet. Monitor the logs to confirm indexing progress. The process is complete when electrs reports that it has indexed up to the current block height and the delay between new blocks arriving and being indexed drops to under a second.
Configuring Wasabi Wallet to use a custom Electrum server
Wasabi Wallet’s configuration file controls which Electrum servers it queries. On Windows, this file is typically located in %APPDATA%\WalletWasabi\Client; on macOS, ~/Library/Application Support/WalletWasabi/Client; on Linux, ~/.walletwasabi/Client. The file is named Settings.json. Before editing, back up the original so you can revert if something goes wrong. Inside Settings.json, locate the section containing ElectrumServers or ServerConfiguration depending on your Wasabi version.
The entry should specify the hostname or IP address of the Electrum server (127.0.0.1 if it is on the same machine), the port it is listening on (typically 50001 for encrypted Electrum protocol or 50002 for cleartext), whether to use TLS encryption, and optionally a certificate fingerprint to verify the server’s identity. If the Electrum server is on the same machine and bound to 127.0.0.1, use 127.0.0.1:50001 as the server address. If it is on another machine on the same network, use that machine’s local IP address (e.g., 192.168.1.50:50001). Do not use the public internet unless you have configured TLS, authentication, and firewall rules carefully.
After editing the configuration file, close Wasabi if it is running and restart it. Upon startup, Wasabi reads the configuration and attempts to connect to the specified Electrum server. Watch the application logs (accessible via Help > Show Logs in the GUI) for connection confirmation or error messages. If the connection fails, common causes are a typo in the address, the Electrum server not actually listening on that port, a firewall blocking the connection, or the Electrum server not being fully indexed yet. Verify each of these in order before assuming a configuration error.
Testing connectivity and verifying blockchain data
Once Wasabi reports a successful connection to the custom Electrum server, the next step is to verify that data is actually flowing through the local infrastructure. Create a test wallet or load an existing one, and check its balance. The balance should appear quickly (within a few seconds) because queries no longer cross the internet to distant servers. Open the Wallet menu and select Show Advanced or Transactions to view transaction history. Each query should now originate from your local Electrum server, not from Wasabi’s default coordinators.
A more rigorous test is to monitor network traffic on your router or using packet capture tools such as tcpdump or Wireshark. Run Wasabi, perform a wallet balance check, and observe which IP addresses are contacted. If the custom Electrum server is on 192.168.1.50, you should see traffic only to that address and to peer-to-peer Bitcoin network nodes (if your Bitcoin node is establishing outbound connections). You should not see traffic to wasabiwallet.io, blockchain.info, or other third-party services. If unexpected external traffic appears, it may indicate that Wasabi fell back to a default server, a misconfiguration caused it to query multiple servers, or a background process is making additional requests.
Block height verification is another useful check. The Bitcoin node reports the current block height via RPC; the Electrum server reports its indexed height via its logs or via a query. These should match within a block or two. If Wasabi shows an old block height or balance changes slowly, the Electrum server may not be fully synced or may be falling behind new blocks. Confirm that both Bitcoin Core and electrs are running and making progress before investigating wallet behavior.
CoinJoin mixing with personal infrastructure
Once wallet queries are routed through the custom Electrum server, CoinJoin mixing can proceed using Wasabi’s normal workflows. The mixing coordination and transaction broadcasting still use Wasabi’s public infrastructure; what changes is that balance queries and address-scanning queries no longer leak to third parties. When you initiate a CoinJoin round, Wasabi queries the Electrum server for your UTXO set, calculates which inputs are available to mix, and then communicates with the Wasabi coordinator to arrange the mix.
The mixing transaction itself is still broadcast to the Bitcoin peer-to-peer network and appears on the public blockchain. An external observer can still analyze the transaction structure, timing, and correlations with other data. What they cannot observe is that you initiated the query or which addresses you were interested in beforehand. The privacy benefit is real but specific: it prevents blockchain surveillance companies from seeing the moment before the transaction when you checked your balance or from correlating balance queries to transaction broadcasts.
For higher-value mixing or if you want to eliminate coordinator dependency as well, consider running a private coordinator. This is significantly more complex than running an Electrum server and is outside the scope of this guide. The reward is that neither Wasabi’s coordinators nor any other third party observes even that you are participating in a mix round. For most users, the personal Electrum server represents an acceptable balance between privacy gains and operational overhead.
Maintenance, monitoring, and long-term operation
A self-hosted infrastructure requires ongoing attention. Bitcoin Core should receive security updates promptly; electrs should be rebuilt occasionally to incorporate performance improvements and bug fixes. Set up monitoring to alert you if either process stops unexpectedly. A simple cron job that checks whether Bitcoin Core and electrs are running and restarts them if not is a common solution. More sophisticated setups use systemd, Docker, or dedicated monitoring software such as Prometheus.
Disk space is a practical constraint. Bitcoin Core’s blockchain grows by approximately 50–60 GB per year as the network processes transactions. On a limited SSD, this will eventually exhaust capacity. Plan for storage expansion every 2–3 years, or use an external USB drive (accepting slightly slower performance). The Electrum server index also grows but typically stays under 100 GB total. Ensure backups of critical data: for Wasabi, this is the wallet file (encrypted) and recovery phrase (stored offline). For the Bitcoin node, backups are less critical because the blockchain can be redownloaded, though the initial sync is time-consuming.
When you access Wasabi Wallet documentation, you may find community resources discussing server configurations and troubleshooting steps. The official Wasabi repository on GitHub also includes discussions about Electrum server compatibility and known issues with specific versions. Engaging with that community can help you navigate edge cases and stay informed about best practices as the software evolves.
Network security also deserves attention. If the Electrum server or Bitcoin node is accessible from the internet or a network with devices you do not fully control, use a firewall to restrict access and consider VPN or Tor to anonymize the Bitcoin node’s peer connections. A Bitcoin node that makes outbound connections to peers reveals your IP address to those peers; they do not learn what addresses you hold, but they know you are running a node. Running Bitcoin Core behind Tor can mitigate this, though sync speed may decrease.
When personal infrastructure is worth the effort
Not every Bitcoin user needs a personal Electrum server. The operational overhead, hardware cost, and maintenance burden make sense primarily for users who fit certain criteria. First, you should already be running a full Bitcoin node or committed to running one. Second, you should be conducting high-value transactions where the privacy loss from Electrum server queries represents a meaningful risk. Third, you should be comfortable with command-line configuration and willing to troubleshoot when something breaks.
For users mixing large balances, conducting frequent transactions, or operating in jurisdictions with aggressive financial surveillance, a personal Electrum server adds meaningful privacy without requiring dramatic lifestyle changes. The infrastructure is relatively inexpensive to run in perpetuity if you already have hardware available. For casual users checking small balances occasionally, the default Wasabi setup with open-source wallet guarantees and CoinJoin mixing provides substantial privacy without the added complexity.
The ideal case is a user who understands that privacy is layered. They recognize that a desktop wallet with CoinJoin protects the blockchain transaction, that a Wasabi setup with careful fee management and address practices protects transaction patterns, and that a personal Electrum server protects the pre-transaction query phase. Each layer is imperfect, but together they raise the cost of surveillance substantially. That is the realistic privacy goal: not perfect anonymity, but sufficient friction that casual observation becomes impractical and targeted surveillance requires resources beyond what most threats can justify.
Frequently asked questions
Does using a personal Electrum server make my Bitcoin transactions anonymous on the blockchain?
No. A personal Electrum server prevents third parties from observing your wallet queries, but it does not change the transaction structure on the blockchain itself. CoinJoin mixing, available in Wasabi, is what obscures transaction relationships on the public ledger. The Electrum server and CoinJoin are complementary privacy controls, not substitutes for each other.
Can I run an Electrum server on a Raspberry Pi alongside Bitcoin Core?
Yes, though performance will be slower than on faster hardware. Initial blockchain sync may take 24–48 hours, and indexing may take 12–24 hours. A Raspberry Pi 4 with 8 GB RAM and a USB SSD is the practical minimum. Accept that queries may take a second or two longer than on desktop hardware, and monitor disk space and temperature.
What happens to my Wasabi wallet if the Electrum server goes offline?
Wasabi will attempt to reconnect to the server and will show a connection error in the status bar. If the server remains offline, you can either start it again or temporarily reconfigure Wasabi to use a default public Electrum server. Your wallet funds are not affected; they remain secured by your private key, which Wasabi controls locally. No transaction data is lost.