> 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/transaction-finality-and-legal-certainty-on-bsv/the-relationship-between-block-inclusion-and-spv-verification.md).
# The Relationship Between Block Inclusion and SPV Verification
While the first-seen rule provides practical finality within seconds, **SPV verification** becomes possible once a transaction is included in a block. The average time for transaction inclusion is approximately **5 minutes**. Once included, the transaction can be verified using a **Merkle proof** that cryptographically binds it to the block header.
Here's the critical distinction for developers: **finality** (the point at which a transaction cannot be reversed) occurs when the transaction reaches network consensus under the **first-seen rule**, but **SPV verification** (the ability to prove that finality cryptographically) occurs when the transaction is included in a block. Both are important for compliance, but they serve different purposes. **Finality determines when a transaction is legally binding**; SPV verification provides the cryptographic proof of that transaction's existence and timing.
---
# 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/transaction-finality-and-legal-certainty-on-bsv/the-relationship-between-block-inclusion-and-spv-verification.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.
