> 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/block-confirmation-depth-and-proof-stability.md).
# Block Confirmation Depth and Proof Stability
With each subsequent block added to the blockchain, the probability that the initial block containing your transaction will be orphaned decreases exponentially. While the BSV first-seen rule means the transaction itself remains valid and final even during chain reorganizations, the **stability of the SPV proof** increases with confirmation depth.
For legal compliance purposes, this confirmation depth provides **increasing levels of proof certainty**. A transaction with one confirmation (included in the most recent block) has cryptographic proof of inclusion. A transaction with six confirmations has proof that has been validated by subsequent miners over approximately 30 minutes of network time. A transaction with 100 confirmations represents proof validated over more than 8 hours of continuous network operation.
Different compliance contexts may require different confirmation depths. A payment processor releasing digital goods might accept transactions after one confirmation. A property title transfer system might require six confirmations. International financial reporting might specify 100 confirmations for the fiscal year-end audit trail. The key insight for developers is that **SPV proofs remain valid regardless of confirmation depth**—the Merkle proof structure doesn't change—but the **certainty that the proof will never need to be updated** increases with each new block.
---
# 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/block-confirmation-depth-and-proof-stability.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.
