Connect your Bitcoin wallet to your own node
Reduce address-query disclosure with a supported private backend and understand the limits of Tor and on-chain privacy.
The quick answer
A wallet that queries a public backend can disclose addresses or account information to that operator. A properly configured connection to your own node gives you more control over those queries.
Network privacy and transaction privacy differ
Some wallets connect directly to Bitcoin Core; others need an Electrum-compatible server. Tor can hide some network metadata, but does not erase public links between transaction inputs and outputs.
Step by step
- 1
Choose a supported backend
Read your wallet's official connection guide. Check whether it needs RPC, an Electrum server or another interface, and account for index storage.
- 2
Keep access private
Prefer local or securely authenticated private connections. Follow documented Tor or remote-access setup without opening unrestricted RPC to the internet.
- 3
Verify the active connection
Check the displayed server, sync status and fallback settings. Compare wallet history after reconnecting, and know what happens if your node is unavailable.
Worked example
Pointing an Electrum-only wallet at Bitcoin Core's RPC port will not create a working Electrum service. The backend protocol must match.
Before you continue
A related question
Is an extended public key safe to share with a server?
It cannot normally spend by itself, but can expose a large part of an account's addresses and history. Share it only with services you intend to trust with that information.
Try it with a tool
Sources & further reading
Source links checked on 15 Oct 2026. Examples explain the mechanics; provider fees and features can change.
- Sparrow Wallet sparrowwallet.com
- Bitcoin.org bitcoin.org
