Skip to article
Degrees of SatoshiFollow the connections.
SearchTrace an address
Degrees of Satoshi/ Encyclopedia

Encyclopedia How the network works · Entry 94

SPV wallets: what a lightweight Bitcoin check can establish

AI-assisted research · separate automated verificationCorrections

Theme
How the network works
Sources
4 cited records
Reading time
About 3 minutes
Automated verification
Substantive update
In this article

At a glance

Key facts

Key facts for SPV wallets: what a lightweight Bitcoin check can establish
FactDetailSource
DataThe design uses headers plus transaction inclusion information.[1]
AssumptionIts assurances depend on the chain view and honest-network assumptions described in the paper.[1]
DistinctionA wallet that trusts an explorer response is not necessarily performing SPV.[1]
01

What the small client can establish

A header commits to a transaction tree and links to the preceding header. With an inclusion branch, a client can check the payment against that commitment and observe work accumulated after the block.

The white paper explicitly distinguishes this from checking the transaction for oneself. A concise proof is useful, but its scope should be described accurately.

02

Why a full node has a different role

A fully validating node checks transactions and blocks against consensus rules, including whether inputs exist and their spending conditions are met. Merely following the most-work headers omits those full-data checks.

A pruned full node can still perform validation while discarding old block bodies afterward. Low retained disk usage and SPV are therefore not synonyms.

03

Ask what the wallet actually verifies

“Light wallet” covers several designs. Some consult one service, some download headers, and some use other filtering or proof arrangements. The label alone does not identify the verification model.

Identify who supplies data, what the client verifies locally and how it handles conflicting chain views. These details determine what a displayed confirmation count means.

Direct answers

Questions people ask

Is a pruned Bitcoin node an SPV client?

No. Pruning concerns which old files a node retains after validation. SPV changes which information the client downloads and which rules it can independently check.

Inspect the evidence

The answer and key facts have stable claim links. These records retain the scope and qualification when reused.

Simplified Payment Verification, described in section 8 of the Bitcoin white paper, uses block headers and a Merkle branch to check that a payment appears in a chain with accumulated proof of work. It avoids downloading every full block but does not independently validate every transaction rule as a full node does.

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:23.891Z.

Link to this claim
Data: The design uses headers plus transaction inclusion information.

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:23.891Z.

Link to this claim
Assumption: Its assurances depend on the chain view and honest-network assumptions described in the paper.

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:23.891Z.

Link to this claim
Distinction: A wallet that trusts an explorer response is not necessarily performing SPV.

Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T18:15:23.891Z.

Link to this claim
Revision history
  1. — Initial Bitcoin encyclopedia entry at this permanent URL.
  2. — Added reusable claims, explicit source locators, and matching Markdown and JSON. This publishing change does not itself establish factual verification.

Source register

Sources and references

Retrieval dates and locators are recorded individually.
  1. Bitcoin: A Peer-to-Peer Electronic Cash SystemSatoshi Nakamoto

    Most-work chain selection, Merkle inclusion, SPV limits and transaction change.

    Locator: Sections 4–5 and 7–11 · Version / scope: 2008 paper · Retrieved: 2026-10-02T17:03:41.335ZOpen source
  2. Bitcoin Developer Guide: Block ChainBitcoin developer documentation contributors

    Block headers, transaction Merkle trees and competing valid branches.

    Locator: Proof Of Work; Block Height And Forking; Transaction Data · Retrieved: 2026-10-02T17:03:41.181ZOpen source
  3. Bitcoin Developer Guide: TransactionsBitcoin developer documentation contributors

    UTXO inputs, transaction outputs, change and the difference paid as a fee.

    Locator: P2PKH Script Validation; Transaction Fees And Change · Retrieved: 2026-10-02T17:03:41.190ZOpen source
  4. Bitcoin Core 0.11.0 release notesBitcoin Core

    Pruning removes old block files after validation while retaining chainstate.

    Locator: Block file pruning · Version / scope: Bitcoin Core 0.11.0 historical introduction · Retrieved: 2026-10-02T17:03:41.974ZOpen source
How this article was made

Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.

Editorial method and corrections

Degrees of Satoshi editorial project. “SPV wallets: what a lightweight Bitcoin check can establish.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/simplified-payment-verification/