> 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/understanding-transaction-finality-in-bsv.md). # Understanding Transaction Finality in BSV **Transaction finality**—the point at which a transaction becomes irreversible—is a critical concept for legal compliance. Unlike traditional payment systems where finality may take days (as with credit card settlements or bank transfers), blockchain systems offer different finality models with distinct implications for legal certainty. BSV implements the **first-seen rule**, which means transactions achieve practical finality as soon as they reach **100% of network hash power**. This typically occurs within a few seconds of broadcast. Once miners have received a transaction, the probability of it being replaced is effectively zero for all practical applications. This rapid finality is crucial for compliance systems that must make real-time decisions based on transaction status—payment processors determining whether to release goods, compliance systems deciding whether a transaction triggers reporting requirements, or audit systems recording the precise timing of financial events. --- # 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/understanding-transaction-finality-in-bsv.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.