> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-network-topology/spv-wallets-unlocking-simplified-payment-verification-for-secure-transactions/merkle-paths-and-block-headers.md).
# Merkle Paths and Block Headers
To understand SPV, it is vital to grasp the concepts of **Merkle paths** and **block headers**.
#### Merkle Paths
A Merkle path is **a cryptographic proof that demonstrates the existence of a specific transaction** within a block without the need to examine every transaction in that block. This is achieved by providing a path of hashes that leads from the transaction in question to the root of the Merkle tree, which is a **structure that organizes transactions within a block**.
#### Block Headers
Block headers serve as **summaries of blocks in the blockchain**. Each header contains essential information, including a reference to the **previous block, a timestamp, and a Merkle root hash** that represents all transactions in that block. Instead of downloading the entire blockchain, SPV clients only need to access these headers, which significantly reduces the data load—approximately **65MB compared to the full blockchain size**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-network-topology/spv-wallets-unlocking-simplified-payment-verification-for-secure-transactions/merkle-paths-and-block-headers.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
