> 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/bsv-network-topology/spv-wallets-unlocking-simplified-payment-verification-for-secure-transactions/spv-verification-process.md).

# SPV Verification Process

<figure><img src="https://3421145409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRTEKu4E7Fvtss3GI9CYU%2Fuploads%2FHBkCG2Gpoov0HNUsKSyL%2Fveri.gif?alt=media&amp;token=96d0f927-684f-4b46-b215-b9f41342fab0" alt=""><figcaption></figcaption></figure>

The **SPV verification process** is a streamlined method that allows users to confirm the validity of transactions efficiently. The process involves several key steps:

1. **Transaction Inputs Validation**: SPV checks that the inputs of a transaction are unspent and valid. This involves tracing each input back to its original output in the blockchain, ensuring that there are no double-spends.
2. **Script Validation and Fee Checks**: After validating the inputs, the wallet software performs script validation to ensure that all conditions for transferring the inputs are met. This includes verifying cryptographic signatures and ensuring that the transaction includes sufficient fees according to current network requirements.
3. **Transaction Submission to ARC**: Once the transaction passes initial validations, it is sent to the **ARC**, which acts as a transaction processor. ARC performs an additional layer of validation to ensure that no other transactions have attempted to spend the same inputs in the meantime.
4. **Block Inclusion and Final Confirmation**: The ultimate confirmation of a transaction's validity occurs with its inclusion in a block, which happens approximately every 10 minutes. This step ensures that the transaction has been accepted by the network.
5. **Timing**: The initial SPV checks are nearly instantaneous, typically taking just a few milliseconds, while the validation process with ARC takes about 3 seconds, providing rapid feedback on the transaction's status.

This efficient verification process not only accelerates transactions but also ensures compliance with network rules, making SPV ideal for applications requiring fast and reliable transaction verification.


---

# 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/bsv-network-topology/spv-wallets-unlocking-simplified-payment-verification-for-secure-transactions/spv-verification-process.md?ask=<question>&goal=<user_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.
