{
  "$schema": "https://degreesofsatoshi.com/encyclopedia/schemas/article-v1.json",
  "schemaVersion": "1.0.0",
  "id": "bitcoin-node-vs-wallet-server",
  "canonical": "https://degreesofsatoshi.com/encyclopedia/bitcoin-node-vs-wallet-server/",
  "collection": "bitcoin",
  "title": "Your Bitcoin node versus a wallet server: who supplies the answers?",
  "description": "Compare a wallet’s use of public servers with a personal Bitcoin node and understand which privacy and verification assumptions change.",
  "aliases": [
    "bitcoin node electrum server",
    "bitcoin node electrum server explained"
  ],
  "dates": {
    "published": "2026-10-02",
    "modified": "2026-10-02",
    "verified": "2026-10-02T19:29:20.637Z",
    "dataAsOf": "2026-10-02"
  },
  "authorship": {
    "publisher": "Degrees of Satoshi editorial project",
    "process": "AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied."
  },
  "quickAnswer": {
    "text": "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.",
    "claimId": "bitcoin-node-vs-wallet-server-quick-answer",
    "sourceIds": [
      "x425-btc-electrum-faq",
      "x425-btc-core-running",
      "x425-btc-dev-wallets"
    ]
  },
  "keyFacts": [
    {
      "label": "Wallet server",
      "value": "Can learn the set of addresses queried",
      "sourceIds": [
        "x425-btc-electrum-faq"
      ],
      "id": "wallet-server",
      "claimId": "bitcoin-node-vs-wallet-server-fact-wallet-server"
    },
    {
      "label": "SPV check",
      "value": "Does not prevent every omission by a server",
      "sourceIds": [
        "x425-btc-electrum-faq"
      ],
      "id": "spv-check",
      "claimId": "bitcoin-node-vs-wallet-server-fact-spv-check"
    },
    {
      "label": "Personal setup",
      "value": "May need a server layer as well as a node",
      "sourceIds": [
        "x425-btc-electrum-faq"
      ],
      "id": "personal-setup",
      "claimId": "bitcoin-node-vs-wallet-server-fact-personal-setup"
    }
  ],
  "prerequisites": [
    "simplified-payment-verification",
    "watch-only-wallets"
  ],
  "sections": [
    {
      "id": "path",
      "heading": "Trace the wallet’s actual connection",
      "sourceIds": [
        "x425-btc-electrum-faq"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "example",
      "heading": "A private seed does not make queries private",
      "sourceIds": [
        "x425-btc-electrum-faq",
        "x425-btc-bip32"
      ],
      "paragraphs": [
        "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."
      ]
    },
    {
      "id": "limits",
      "heading": "A personal node still needs a trustworthy connection",
      "sourceIds": [
        "x425-btc-electrum-faq",
        "x425-btc-core-rpc"
      ],
      "paragraphs": [
        "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."
      ]
    }
  ],
  "faq": [
    {
      "question": "Does a watch-only wallet protect my transaction privacy automatically?",
      "answer": "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.",
      "sourceIds": [
        "x425-btc-electrum-faq",
        "x425-btc-bip32"
      ]
    },
    {
      "question": "Can a wallet server hide a transaction without forging a block?",
      "answer": "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.",
      "sourceIds": [
        "x425-btc-electrum-faq"
      ]
    }
  ],
  "claims": [
    {
      "id": "bitcoin-node-vs-wallet-server-quick-answer",
      "articleSlug": "bitcoin-node-vs-wallet-server",
      "statement": "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.",
      "sourceIds": [
        "source-82375415e215e2f2",
        "source-cb92ea1a2a21982c",
        "source-38ff15e10892f1ee"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-82375415e215e2f2",
          "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?"
        },
        {
          "sourceId": "source-cb92ea1a2a21982c",
          "locator": "What Is A Full Node?; Initial Block Download; Network Configuration; Reduce Storage; Disable listening"
        },
        {
          "sourceId": "source-38ff15e10892f1ee",
          "locator": "Wallet Programs; Full-Service Wallets; Signing-Only Wallets; Wallet Files; Hierarchical Deterministic Key Creation; Loose-Key Wallets"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "Educational explanation. Product-specific behavior is scoped to the cited documentation, checked 2026-10-02.",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:29:20.637Z",
        "reviewer": "Independent automated verification — Codex /root/verify_ethereum_100, separate from the Bitcoin drafting agent",
        "notes": [
          "Read Electrum FAQ main-server history, SPV, unconfirmed-data trust, omission and address/IP exposure. A personal node alone does not configure an Electrum connection; watch-only key protection does not remove server observation."
        ]
      }
    },
    {
      "id": "bitcoin-node-vs-wallet-server-fact-wallet-server",
      "articleSlug": "bitcoin-node-vs-wallet-server",
      "statement": "Wallet server: Can learn the set of addresses queried",
      "sourceIds": [
        "source-82375415e215e2f2"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-82375415e215e2f2",
          "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?"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:29:20.637Z",
        "reviewer": "Independent automated verification — Codex /root/verify_ethereum_100, separate from the Bitcoin drafting agent",
        "notes": [
          "Read Electrum FAQ main-server history, SPV, unconfirmed-data trust, omission and address/IP exposure. A personal node alone does not configure an Electrum connection; watch-only key protection does not remove server observation."
        ]
      }
    },
    {
      "id": "bitcoin-node-vs-wallet-server-fact-spv-check",
      "articleSlug": "bitcoin-node-vs-wallet-server",
      "statement": "SPV check: Does not prevent every omission by a server",
      "sourceIds": [
        "source-82375415e215e2f2"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-82375415e215e2f2",
          "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?"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:29:20.637Z",
        "reviewer": "Independent automated verification — Codex /root/verify_ethereum_100, separate from the Bitcoin drafting agent",
        "notes": [
          "Read Electrum FAQ main-server history, SPV, unconfirmed-data trust, omission and address/IP exposure. A personal node alone does not configure an Electrum connection; watch-only key protection does not remove server observation."
        ]
      }
    },
    {
      "id": "bitcoin-node-vs-wallet-server-fact-personal-setup",
      "articleSlug": "bitcoin-node-vs-wallet-server",
      "statement": "Personal setup: May need a server layer as well as a node",
      "sourceIds": [
        "source-82375415e215e2f2"
      ],
      "sourceLocators": [
        {
          "sourceId": "source-82375415e215e2f2",
          "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?"
        }
      ],
      "scope": {
        "collection": "bitcoin",
        "dataAsOf": "2026-10-02",
        "blockHeight": null
      },
      "qualification": "",
      "evidenceStatus": "documented",
      "verification": {
        "status": "verified",
        "method": "independent automated source review",
        "checkedAt": "2026-10-02T19:29:20.637Z",
        "reviewer": "Independent automated verification — Codex /root/verify_ethereum_100, separate from the Bitcoin drafting agent",
        "notes": [
          "Read Electrum FAQ main-server history, SPV, unconfirmed-data trust, omission and address/IP exposure. A personal node alone does not configure an Electrum connection; watch-only key protection does not remove server observation."
        ]
      }
    }
  ],
  "sources": [
    {
      "id": "x425-btc-electrum-faq",
      "label": "Frequently Asked Questions",
      "publisher": "Electrum",
      "url": "https://electrum.readthedocs.io/en/latest/faq.html",
      "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?",
      "note": "Electrum-specific sweep/import distinctions, seed recovery scope and address discovery.",
      "checkedAt": "2026-10-02T18:53:56.378Z",
      "contentSha256": "a7f9a2d109a2a753b0010cda1bd2d789a0417a0788a48ea6632c3fe3b391fb06",
      "recordId": "source-82375415e215e2f2",
      "version": null
    },
    {
      "id": "x425-btc-core-running",
      "label": "Running a Full Node",
      "publisher": "Bitcoin.org",
      "url": "https://bitcoin.org/en/full-node",
      "locator": "What Is A Full Node?; Initial Block Download; Network Configuration; Reduce Storage; Disable listening",
      "note": "Operational roles, synchronization, inbound/outbound connections and version-dependent resource guidance.",
      "checkedAt": "2026-10-02T18:53:56.154Z",
      "contentSha256": "69230ccdb4acb9a5f6064154f025a5b133bad08fee2b842353e556488dec06d7",
      "recordId": "source-cb92ea1a2a21982c",
      "version": null
    },
    {
      "id": "x425-btc-dev-wallets",
      "label": "Wallets",
      "publisher": "Bitcoin developer documentation",
      "url": "https://developer.bitcoin.org/devguide/wallets.html",
      "locator": "Wallet Programs; Full-Service Wallets; Signing-Only Wallets; Wallet Files; Hierarchical Deterministic Key Creation; Loose-Key Wallets",
      "note": "Wallet types, generated keys, deterministic wallets and offline signing.",
      "version": "Developer guide; historical implementation details require qualification",
      "checkedAt": "2026-10-02T18:53:53.756Z",
      "contentSha256": "1f3433f0ffac2ee2cc1d0d3ff1ac60ebaf68a92826dd813c8b312581a64344e0",
      "recordId": "source-38ff15e10892f1ee"
    },
    {
      "id": "x425-btc-bip32",
      "label": "Hierarchical Deterministic Wallets",
      "publisher": "Bitcoin Improvement Proposals",
      "url": "https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0032.mediawiki",
      "locator": "Motivation; Extended keys; Security",
      "note": "Deterministic key derivation, backup scope and public/private child derivation.",
      "version": "Pinned BIPs revision",
      "checkedAt": "2026-10-02T18:53:54.013Z",
      "contentSha256": "e5e00a8289db2f681052cf24a745320afc225e66b25d1e489a7c884d2fc7f11f",
      "recordId": "source-225ce32b9f96878c"
    },
    {
      "id": "x425-btc-core-rpc",
      "label": "JSON-RPC interface",
      "publisher": "Bitcoin Core",
      "url": "https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/JSON-RPC-interface.md",
      "locator": "Introduction; Endpoints; Versioning; Security; RPC consistency guarantees",
      "note": "Privileged RPC scope, authentication, local access and unencrypted transport limitations.",
      "version": "Bitcoin Core v29.0",
      "checkedAt": "2026-10-02T18:53:55.910Z",
      "contentSha256": "c56badff1616ff19b112ebbc97d600726101ca8e8fa2c91b15b901b96c938930",
      "recordId": "source-84123e4e42fca415"
    }
  ],
  "related": {
    "articles": [
      "simplified-payment-verification",
      "watch-only-wallets",
      "bitcoin-nodes-explained",
      "bitcoin-node-initial-sync",
      "bitcoin-rescan-vs-reindex"
    ],
    "dossiers": [],
    "wallets": []
  },
  "revisionHistory": [
    {
      "date": "2026-10-02",
      "kind": "published",
      "summary": "First publication after primary-source research and separate automated verification."
    }
  ],
  "citation": "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/"
}