# Your Bitcoin node versus a wallet server: who supplies the answers? A Bitcoin wallet needs a source of chain information, but that source is not always a full node running on the same device. Some wallets query a server for address history and proofs. A personal node, sometimes paired with a wallet-server index, changes who supplies those answers. It can reduce third-party exposure, but only if the wallet actually connects to the intended system and uses its results correctly. Evidence: [Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html); [Running a Full Node](https://bitcoin.org/en/full-node); [Wallets](https://developer.bitcoin.org/devguide/wallets.html) Canonical: https://degreesofsatoshi.com/encyclopedia/bitcoin-node-vs-wallet-server/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:29:20.637Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Wallet server:** Can learn the set of addresses queried ([Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html)) - **SPV check:** Does not prevent every omission by a server ([Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html)) - **Personal setup:** May need a server layer as well as a node ([Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html)) ## Trace the wallet’s actual connection Electrum describes a client-server design in which a main server supplies wallet history and broadcasts the client’s transactions. The client verifies confirmed transactions through SPV, but the server can omit relevant history and is trusted for unconfirmed transaction information. The server can also associate requested script information and observe the connecting network address. An encrypted connection protects transport; it does not prevent the server itself from seeing the requests it serves. Evidence: [Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html) ## A private seed does not make queries private Suppose a watch-only wallet queries one server about 30 derived receiving addresses. It sends no private key, yet the server can reasonably associate those addresses with one client. The signer remaining offline addresses key exposure, not this address-clustering issue. Using your own compatible server can move that observation to infrastructure you control. Confirm the application has not silently fallen back to a public server. Evidence: [Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html); [Hierarchical Deterministic Wallets](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0032.mediawiki) ## A personal node still needs a trustworthy connection Running a node somewhere does not automatically make every wallet use it. Check the wallet’s documented server or node configuration and its authentication behavior. Electrum’s protocol is distinct from Core’s administrative RPC, so the two interfaces are not interchangeable. Protect access to the node and server host. Core warns that someone controlling the machine can compromise its reported results or privileged interface. Independent validation is useful only within a trustworthy end-to-end setup. Evidence: [Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html); [JSON-RPC interface](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/JSON-RPC-interface.md) ## Questions ### Does a watch-only wallet protect my transaction privacy automatically? No. It can avoid storing spending keys, but queries can reveal related addresses to the server. Spending authority and network-observation privacy are different properties. Evidence: [Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html); [Hierarchical Deterministic Wallets](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0032.mediawiki) ### Can a wallet server hide a transaction without forging a block? Yes. Electrum’s documentation notes that a server can lie by omission, failing to mention relevant history. A valid inclusion proof for one transaction does not prove the server supplied every relevant transaction. Evidence: [Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html) ## Claims and scope ### bitcoin-node-vs-wallet-server-quick-answer A Bitcoin wallet needs a source of chain information, but that source is not always a full node running on the same device. Some wallets query a server for address history and proofs. A personal node, sometimes paired with a wallet-server index, changes who supplies those answers. It can reduce third-party exposure, but only if the wallet actually connects to the intended system and uses its results correctly. Educational explanation. Product-specific behavior is scoped to the cited documentation, checked 2026-10-02. Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### bitcoin-node-vs-wallet-server-fact-wallet-server Wallet server: Can learn the set of addresses queried Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### bitcoin-node-vs-wallet-server-fact-spv-check SPV check: Does not prevent every omission by a server Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### bitcoin-node-vs-wallet-server-fact-personal-setup Personal setup: May need a server layer as well as a node Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Frequently Asked Questions](https://electrum.readthedocs.io/en/latest/faq.html) — Electrum. Electrum-specific sweep/import distinctions, seed recovery scope and address discovery. Locator: Does Electrum trust servers?; Can I import private keys from other Bitcoin clients?; Can I sweep private keys from other Bitcoin clients?; What is the gap limit?; How do I upgrade Electrum?. Retrieved: 2026-10-02T18:53:56.378Z. - [Running a Full Node](https://bitcoin.org/en/full-node) — Bitcoin.org. Operational roles, synchronization, inbound/outbound connections and version-dependent resource guidance. Locator: What Is A Full Node?; Initial Block Download; Network Configuration; Reduce Storage; Disable listening. Retrieved: 2026-10-02T18:53:56.154Z. - [Wallets](https://developer.bitcoin.org/devguide/wallets.html) — Bitcoin developer documentation. Wallet types, generated keys, deterministic wallets and offline signing. Locator: Wallet Programs; Full-Service Wallets; Signing-Only Wallets; Wallet Files; Hierarchical Deterministic Key Creation; Loose-Key Wallets. Retrieved: 2026-10-02T18:53:53.756Z. - [Hierarchical Deterministic Wallets](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0032.mediawiki) — Bitcoin Improvement Proposals. Deterministic key derivation, backup scope and public/private child derivation. Locator: Motivation; Extended keys; Security. Retrieved: 2026-10-02T18:53:54.013Z. - [JSON-RPC interface](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/JSON-RPC-interface.md) — Bitcoin Core. Privileged RPC scope, authentication, local access and unencrypted transport limitations. Locator: Introduction; Endpoints; Versioning; Security; RPC consistency guarantees. Retrieved: 2026-10-02T18:53:55.910Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees of Satoshi editorial project. “Your Bitcoin node versus a wallet server: who supplies the answers?.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/bitcoin-node-vs-wallet-server/