> 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/implementing-finality-checks-in-compliance-systems.md).
# Implementing Finality Checks in Compliance Systems
For developers building compliance systems, understanding finality requires implementing checks at multiple levels. First, systems should track **transaction broadcast** and network propagation to determine first-seen finality. Second, systems should monitor **block inclusion** to enable SPV verification. Third, systems should track **confirmation depth** to determine when proof stability meets specific compliance requirements.
Consider a practical example: A payment processing system receives a transaction at timestamp T₀. Within 2-3 seconds (T₀ + 3s), the transaction reaches network consensus (first-seen finality). The system can now safely release digital goods or proceed with the transaction. At T₀ + 5m (approximately), the transaction is included in a block, and the system generates an **SPV proof** for compliance records. At T₀ + 30m (six confirmations), the system marks the transaction as having high proof stability, suitable for financial reporting. At T₀ + 8h (100 confirmations), the system archives the transaction with its SPV proof as part of the permanent audit trail.
---
# 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/implementing-finality-checks-in-compliance-systems.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.
