Bitcoin Whitepaper — Annotated Guide

# 8. Simplified Payment Verification

It is possible to verify payments without running a full network node. A user only needs to keep a copy of the block headers of the longest proof-of-work chain, which he can get by querying network nodes until he's convinced he has the longest chain, and obtain the Merkle branch linking the transaction to the block it's timestamped in. He can't check the transaction for himself, but by linking it to a place in the chain, he can see that a network node has accepted it, and blocks added after it further confirm the network has accepted it.

> 💡 In plain terms
> Running a "full node" means downloading and verifying every single Bitcoin transaction ever made — currently over 500 GB of data. That's not practical for a phone or laptop.
>
> Simplified Payment Verification (SPV) is Bitcoin's lightweight alternative.
>
> An SPV client only downloads block headers — tiny 80-byte summaries of each block.
> Then, when you need to verify a specific transaction, it asks the network:
> "Give me the Merkle branch proving this transaction is in that block."
>
> The Merkle branch is a small set of hashes that lets you mathematically prove a transaction is included in a block, without downloading the whole block.
> It's like proving a specific page exists in a book by checking only the table of contents and a cryptographic bookmark — you don't need to read the entire book.

As such, the verification is reliable as long as honest nodes control the network, but is more vulnerable if the network is overpowered by an attacker. While network nodes can verify transactions for themselves, the simplified method can be fooled by an attacker's fabricated transactions for as long as the attacker can continue to overpower the network. One strategy to protect against this would be to accept alerts from network nodes when they detect an invalid block, prompting the user's software to download the full block and alerted transactions to confirm the inconsistency. Businesses that receive frequent payments will probably still want to run their own nodes for more independent security and quicker verification.

> 💡 In plain terms
> SPV has a trade-off worth understanding:
>
> SPV relies on the assumption that the longest chain is the honest chain.
> If an attacker somehow controlled the majority of mining power, they could theoretically feed an SPV client false information.
>
> That's why Satoshi notes that businesses handling large volumes should run their own full nodes — they have the strongest security guarantees because they verify everything themselves, trusting no one else's data.
>
> SPV is best thought of as a practical compromise: good enough for everyday payments, while full nodes remain the gold standard for entities who need maximum security (exchanges, merchants, payment processors).

> ⚡ Why It Works vs. Traditional Finance
> To verify a bank transaction today, you call your bank — or you trust the app they built.
> You have no independent way to verify the bank's record is correct.
> You are entirely dependent on the bank's honesty and competence.
>
> With Bitcoin SPV:
> - Anyone can verify any transaction using only public data
> - No account needed, no permission needed, no API key needed
> - The same cryptographic proof that the full network uses is accessible to a mobile phone
> - And if something looks wrong, you can always escalate to running a full node
>
> Bitcoin makes financial self-sovereignty accessible to anyone with a modest device, not just institutions with enterprise database infrastructure.

Bitcoin Simplified Payment Verification

// COMMENTS

ON THIS PAGE