> 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/features-spv-wallet-reference-implementation.md).
# Features: SPV Wallet Reference Implementation
The **BSV Association's SPV Wallet** is an open-source, non-custodial wallet designed specifically for the BSV blockchain. It serves as a reference implementation for Simplified Payment Verification, allowing users to verify transactions without running a full node. Key features of the BSV SPV Wallet include:
* **Direct Network Communication**: Enables fast transaction verification by communicating directly with the BSV network.
* **Best Practices and Technical Standards**: Provides guidelines for handling SPV checks effectively.
* **Peer-to-Peer Payment Capabilities**: Facilitates direct transactions between users without intermediaries.
* **Double-Spend Protection Mechanisms**: Ensures that transactions are secure and valid.
* **Integration with Block Headers Service**: Allows for efficient transaction verification by utilizing block headers.
These features ensure that users can manage their digital assets securely and efficiently, aligning with Bitcoin's original vision of a decentralized peer-to-peer payment system.
---
# 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/features-spv-wallet-reference-implementation.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.