SPV Wallet is a free, open-source noncustodial wallet for the BSV blockchain, written in Go and aimed at developers and technically minded users who want a wallet they can run and configure themselves. Because it is noncustodial, the keys you control stay with you rather than with a third-party service. The program is distributed as a Windows build or installer, and the project also lists macOS and Docker as supported platforms.
The latest release is v1.4.1, and the most recent code update is recorded as October 2026, so the project is actively maintained. If you are looking for a simple app for holding many everyday coins, this is not that kind of tool. It is better understood as wallet infrastructure with paymail and BEEF support, documented APIs and a configuration model that suits server-style setups.
What Is a Noncustodial Wallet and Why It Matters
A noncustodial wallet gives you control of the private keys that unlock your funds. Nobody else can move your coins, but nobody else can recover them for you either. That trade-off is the core idea behind self-custody.
With SPV Wallet, the responsibility for backups sits with you. Your seed phrase or key material must be stored safely offline, because losing it means losing access. Many users underestimate this step, so treat backup as the first task after installation, not an afterthought.
Noncustodial software also changes how you think about services. You do not need an account or approval from a provider to receive or send payments. The same freedom means that errors, misconfigurations and phishing attempts are your problem to prevent, which is why careful setup matters more here than in custodial apps.
How Simplified Payment Verification Shapes the Design
Simplified Payment Verification, usually called SPV, is a method for checking that a transaction was included in a block without storing the entire blockchain. The wallet relies on block headers and cryptographic proofs to confirm payments. This approach keeps resource use far lower than running a full node.
The trade-off is that SPV clients depend on data supplied by other nodes, so they verify less than a full node does. Transaction formats such as BEEF help by packaging the ancestry a recipient needs to check a payment. That is why BEEF support is a meaningful part of the project rather than a minor option.
For a Windows user, the practical result is a wallet that can stay responsive on an ordinary computer. The underlying design targets server-style and integration use, so the performance advantage shows most clearly when the wallet runs continuously alongside other services.
Realistic Use Cases for a Developer-Focused BSV Wallet
A small development team might run SPV Wallet as a backend component for a BSV payment flow. The wallet handles addresses, transaction history and paymail routing while the application handles the user interface. The API documentation helps the team map endpoints to their own code.
Another scenario is testing. Because the project includes unit and fuzz tests and a configurable setup, a developer can spin up a test instance, experiment with paymail and BEEF transactions, and reset the environment without touching real funds. Using test configuration and separate keys is essential before any production launch.
A third group is technically confident individuals who want to operate their own wallet service on a home server or in a Docker container. They can adjust environment variables and config files to match their network, then keep the software updated by tracking new releases on GitHub.
Key features
Noncustodial Design
Paymail Support
BEEF Transaction Handling
Flexible Configuration
Storage and Caching Choices
Tested Codebase and Documentation
Supported coins
SPV Wallet is built for the BSV blockchain. It is not a multi-coin application, so it does not cover Bitcoin, Ethereum or other networks. Its paymail and BEEF features are tied to BSV transactions. If you plan to use TAAL services with the wallet, you will need an API key from TAAL before those features will work.
How to install SPV Wallet on Windows
- 1
Get the Program
Download only from the official website or the project's GitHub Releases page at github.com/bitcoin-sv/spv-wallet. Choose the Windows build or installer that matches your system. Avoid mirrors and file-sharing sites, because they may bundle modified or malicious files.
- 2
Verify the File
Compare the SHA-256 checksum of the downloaded file with the value published on the official release page. If a signature is provided, check it as well. Do not run the file if the values do not match, and download it again from the official source.
- 3
Run the Installer or Build
Launch the installer and follow the on-screen prompts, or extract the Windows build to a folder you control. Keep the wallet files in a location with restricted access, because they will hold configuration and database data.
- 4
Set Up Configuration
Decide how you will supply settings: command-line flags for one-off runs, environment variables for secrets, or a config file for stable defaults. Remember that flags override environment variables, and the config file applies only when nothing else sets a value.
-
Add Service Credentials and Start
If you intend to use TAAL services, add your TAAL API key through the appropriate setting. Start the wallet, check that it responds, and read the SPV Wallet Documentation for the endpoints and options relevant to your project.
How to use SPV Wallet
SPV Wallet is driven by configuration and API calls rather than a conventional point-and-click interface, so a clear plan helps. Start with a test setup, confirm each behavior, and only then move to any setup that handles real value.
- Open the API reference on pkg.go.dev and the SPV Wallet Documentation to see which endpoints your use case needs.
- Choose your configuration method. Put stable defaults in the config file, store secrets in environment variables, and use flags for temporary overrides.
- Set your database and cache options. SQLite is the database choice, and freecache handles caching, so confirm that the storage path is writable.
- Start the wallet and check that it responds to a basic request before connecting anything else.
- Test paymail routing with small amounts or a test environment. Remember that signing is disabled, so do not design flows that depend on signed paymail responses.
- If you use TAAL services, add your API key and verify that requests succeed.
- Back up your seed phrase and configuration files to an offline location, then document how to restore the setup.
Run through these steps every time you update to a new release, because configuration names and behavior can change between versions.
Pros & cons
- Free and open source, so you can read the code and build trust through transparency
- Noncustodial design keeps control of keys with the user
- BEEF transaction support is enabled out of the box
- Flexible configuration with flags, environment variables and a config file
- Includes unit tests and fuzz tests built with testify
- Documentation and godocs are available for developers
- Runs on Windows as a build or installer, and also on macOS and Docker
- Aimed at developers and technical users rather than casual holders
- Only the BSV blockchain is covered, so it is not a multi-asset wallet
- Paymail signing is disabled in the current setup
- TAAL services require a separate API key
- Setup involves configuration decisions that beginners may find unfamiliar
- Users who need a polished consumer interface will likely prefer another app
Is SPV Wallet safe?
SPV Wallet is a noncustodial wallet, so safety depends largely on how you handle keys. Download only from the official website or the GitHub Releases page, and verify the SHA-256 checksum or signature before installation. Never enter your seed phrase on a third-party website, in a chat message or in an email, because no legitimate service needs it. Store your backup offline and keep a second copy in a secure location. Because the wallet manages funds, test any new configuration with small amounts first. Paymail signing is disabled in this version, so treat that limitation as a reason for extra caution. Check the latest version on the official website before you update.
- Official source only. Download from github.com/bitcoin-sv/spv-wallet. Ignore ads and lookalike domains.
- Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
- Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
Alternatives
SPV Wallet focuses on one network, the BSV blockchain, and it is built for developers and server-style deployments. Coinomi, Exodus and Atomic Wallet are multi-asset wallets that cover hundreds or thousands of coins, which makes them more practical for someone who wants one app for many tokens. Electron Cash is also a lightweight wallet, but it targets Bitcoin Cash rather than BSV. Trust Wallet on a PC runs as a browser extension, which is a different model from a standalone Go service. Frame is a system-level Web3 wallet for desktop, and Greenery adds bookkeeping features that SPV Wallet does not emphasize. Choose SPV Wallet when BSV, paymail and BEEF matter most and you are comfortable with configuration. Choose a multi-asset wallet when you need broad coin coverage.
Specifications
- Price
- Free
- Type
- Open source
- License
- —
- Latest version
- v1.4.1
- Last update
- 27 Oct 2026
- Windows support
- Yes (Windows build or installer)
- Source code
- github.com/bitcoin-sv/spv-wallet
Frequently asked questions
Yes, SPV Wallet is free and open source. You can download it from the official website or the GitHub Releases page, read the source code and review how it handles keys and transactions. Because it is noncustodial, you are responsible for backups and secure storage of your seed phrase.
Yes, SPV Wallet is available as a Windows build or installer. The project also lists macOS and Docker as supported platforms. Choose the version that matches your setup, verify the file checksum, and follow the configuration steps in the documentation before connecting it to any service.
It can be, if you take standard precautions. Get the program only from the official website or GitHub Releases, verify the SHA-256 checksum, and never enter your seed phrase on third-party sites. Back up your keys offline and test with small amounts before trusting the wallet with significant value.
SPV Wallet is built for the BSV blockchain. It is not designed for Bitcoin, Ethereum or other networks. Its paymail and BEEF features are tied to BSV transactions, so if you need several different coins in one app, a multi-asset wallet will be a better fit.
Paymail is a human-readable address format that looks like an email address and maps to a wallet destination. SPV Wallet has paymail enabled, but signing is disabled. That means you can use paymail routing, but you should not depend on signed paymail responses in this version of the software.
You do not need an API key for the core wallet functions described in the documentation. However, TAAL services require a TAAL API key. Add the key through your configuration settings, and keep it in an environment variable rather than in a shared file.
You can set options with command-line flags, environment variables or a config file. Flags have the highest priority, followed by environment variables, and the config file has the lowest. Review the SPV Wallet Documentation for the available options before you change defaults.
Verdict
SPV Wallet is a good choice for developers and technically confident users who want a free, open-source, noncustodial wallet for the BSV blockchain. It offers paymail routing, BEEF support, flexible configuration and documented APIs, and it runs on Windows as a build or installer. It is not the right tool for someone who wants a simple app holding many coins. Before adopting it, test your setup thoroughly, verify your downloads and keep your backups secure.