# Simplified Payment Verification (SPV)

#### **Instant, Trust-Minimized Verification**

In Bitcoin — and by extension, the BSV blockchain — **Simplified Payment Verification (SPV)** (section 8 of the Bitcoin white paper) allows users to verify transactions without downloading the entire blockchain.

This makes it possible to confirm payments **almost instantly**, even before they are written into a block, through what’s often called a **0-confirmation (0-conf)** transaction.

With the right **wallet**, **point-of-sale configuration**, and **network connectivity** to the BSV node network, small payments can be accepted safely within seconds.

***

#### **How SPV Verification Works**

When a transaction is received, the **interior node values of the Merkle path** linked to the **UTXO** (unspent transaction output) are provided to the new recipient.\
Using these values, the recipient can:

1. **Recalculate the Merkle path authentication proof** for the UTXO.
2. **Compare it against the Merkle Root** stored in the block header of the originating transaction.
3. **Confirm that the UTXO is valid** and that it belongs to the correct proof-of-work chain.

This verification happens **locally and instantly**, without requiring trust in any third party.

<figure><img src="/files/lyaezvqdTE0Y9bqszXQ7" alt=""><figcaption></figcaption></figure>

#### **Network Consensus in Action**

Once verified, the transaction and its Merkle proof are **relayed to a node**, which quickly **propagates it through the network**.

The recipient’s wallet can then query a **random subset of nodes** to check whether the transaction has been seen and validated across the network.

Because of the **“small-world” network topology** of BSV, **over 90% of nodes are within two hops** of one another.

This means that checking with a few random nodes is enough to confidently assume that most of the network — and hence most of the hash power — agrees on the transaction’s validity.

<figure><img src="/files/YnCOHDKdjuXnTBgHa0Na" alt=""><figcaption></figcaption></figure>

#### **Different Views, Same Ledger**

Each node maintains its own **mempool** of unconfirmed transactions.

Because nodes receive transactions in slightly different orders, each may temporarily have a different **Merkle tree state** representing the order in which it saw transactions.

When a miner successfully produces a new block, **their version of the transaction order** (based on the “first-seen” rule) becomes part of the blockchain’s **official record**.

***

#### **From Instant Settlement to Streaming Payments**

SPV enables **instant transaction settlement**, which in turn supports advanced use cases like **payment channels**.

Payment channels use **specific transaction templates** that can evolve through multiple states — where only the final version is recorded on-chain, but all interim updates are secured by **Merkle proofs**.

This allows for **real-time data and value exchange**, including:

* **Video streaming**
* **Voice over IP (VoIP)**
* **Pay-per-calculation services**

Through SPV, the Bitcoin protocol can even **complement legacy Internet protocols** like **TCP/IP** for high-speed, low-latency data transfer.

<figure><img src="/files/sCSKFmts7xq0cmBWZ0wn" alt=""><figcaption></figcaption></figure>

#### **Key Takeaways**

* **SPV** allows transaction verification without downloading the full blockchain.
* **Merkle proofs** make it possible to confirm a transaction’s validity and origin instantly.
* **Network propagation** ensures near-real-time consensus across nodes.
* **Payment channels** build on SPV to enable continuous, low-cost microtransactions.
* This paradigm helps BSV **scale to Internet-level performance**, enabling applications far beyond financial payments.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/bitcoin-primitives-merkle-trees/merkle-trees-and-simplified-payment-verification/simplified-payment-verification-spv.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.