> 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/how-spv-supports-legal-compliance-in-blockchain-technology/legal-compliance-through-verifiable-proof/components-of-compliance-grade-spv-proofs.md).

# Components of Compliance-Grade SPV Proofs

<figure><img src="https://3421145409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRTEKu4E7Fvtss3GI9CYU%2Fuploads%2F7IBGuXYdmgKpj9QydyAC%2FAnatomy%20of%20%20Compliance-Grade%20SPV%20Proof%20.png?alt=media&amp;token=e87d6d4f-b230-43ab-ba86-c07a794e9c87" alt=""><figcaption></figcaption></figure>

A complete SPV proof for legal compliance purposes contains several essential components. First, the **transaction data itself**—including sender, recipient, amount, and any metadata relevant to the transaction. Second, the **transaction hash**—a cryptographic fingerprint uniquely identifying the transaction. Third, the **Merkle proof**—the specific set of hashes linking the transaction to the Merkle root in the block header. Fourth, the **block header** containing the Merkle root, timestamp, and other block metadata. Fifth, **confirmation depth** information—how many subsequent blocks have been added, establishing proof stability.

Together, these components create a compliance record that demonstrates:

* **What** occurred (transaction details)
* **When** it occurred (block timestamp)
* **That it actually occurred** (cryptographic binding to blockchain)
* **That it hasn't been altered** (Merkle proof validation)
* **The stability of this evidence** (confirmation depth)


---

# 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/how-spv-supports-legal-compliance-in-blockchain-technology/legal-compliance-through-verifiable-proof/components-of-compliance-grade-spv-proofs.md?ask=<question>&goal=<user_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.