> 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/spv-fundamentals-and-architecture/understanding-spv-core-principles.md).
# Understanding SPV Core Principles
**Simplified Payment Verification (SPV)** allows participants to verify transactions by downloading only **block headers** rather than complete blocks. This architectural choice dramatically reduces storage requirements while maintaining the cryptographic security guarantees that make blockchain technology valuable for legal compliance.
The SPV model operates on four fundamental principles that developers must understand.
First, **cryptographic verification** ensures that transaction proofs cannot be forged—each transaction's inclusion in the blockchain is mathematically verifiable through **Merkle tree structures**.
Second, **header-only verification** reduces storage requirements from hundreds of gigabytes to mere megabytes while maintaining security guarantees.
Third, **block confirmations** provide increasing cryptographic proof stability as subsequent blocks make changes to the Merkle proof exponentially less likely.
Fourth, the **Merkle proof mechanism** cryptographically binds transactions to block headers, creating verifiable evidence of inclusion that cannot be altered without detection.
---
# 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/spv-fundamentals-and-architecture/understanding-spv-core-principles.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.
