Bchwallet is a free, open-source daemon that handles Bitcoin Cash wallet functionality. It is aimed at developers, node operators and technically confident users who want to run wallet logic on their own machines and interact with it through an RPC interface, rather than through a point-and-click desktop application.
Unlike consumer wallets with graphical screens, Bchwallet runs as a background service. You start it, point other software at it, and let it manage keys, addresses and transactions for Bitcoin Cash. Because the code is published under the ISC license, anyone can read it, audit it or build their own version. That transparency is one of its main strengths, but it also means the software expects a fair amount of technical comfort from its users.
What Is a Wallet Daemon and Why Use One?
A wallet daemon is a program that runs continuously in the background and performs wallet tasks on behalf of other software. Instead of a window with buttons, it exposes an interface that scripts, server applications or other programs can call.
This model is common in exchanges, payment processors and backend services, where a single process must watch addresses, create transactions and track balances without human interaction. Bchwallet follows this approach, which is why it appeals to developers more than to casual users.
If you only want to send and receive Bitcoin Cash from a phone or desktop, a graphical wallet such as Electron Cash is usually the simpler choice.
Who Is Bchwallet For?
Bchwallet fits best with three kinds of users. The first are developers building payment features into websites, apps or internal tools. The second are operators who need a dedicated wallet service running on a server. The third are researchers and enthusiasts who want to study how a wallet backend is structured.
People who are new to command-line tools or who expect a guided setup may find the learning curve steep. Reading the documentation carefully before connecting real funds is strongly recommended.
Because the software is written in Go, contributors familiar with that language can read, modify and extend the code directly, which is another reason it attracts a technical audience.
How HD Wallet Derivation Paths Work
Hierarchical deterministic wallets generate many addresses from a single seed. The derivation path is a string such as m/44'/145'/0' that tells the software which branch of the key tree to use. The number 145 identifies Bitcoin Cash in the BIP44 scheme, while the number after that selects the account.
The separate paths for testnet, regtest and simnet exist so that keys used for experiments never mix with real coins. If you restore a wallet from a seed phrase, you must use the same path that created it, otherwise the software will derive different addresses and appear to show an empty wallet.
Keep a written record of the path you used alongside your seed backup. It is a small detail that saves a great deal of confusion later.
Practical Use Cases
One common use case is a merchant backend that generates a new address for each invoice and watches the blockchain for incoming payments. The JSON-RPC interface allows the web application to request addresses and check balances without storing keys in the web code itself.
Another use is testing. Developers can run Bchwallet on testnet or regtest to simulate payments, verify integrations and catch bugs before any real Bitcoin Cash changes hands.
A third scenario is education. Because the code is open and written in a readable language, instructors can use it to explain how wallets generate keys, track UTXOs and construct transactions.
Key features
Multiple network profiles
Legacy JSON-RPC server
Experimental gRPC server
Supported coins
The project documentation mentions Bitcoin (BTC) and Bitcoin Cash (BCH). Bchwallet is designed around the Bitcoin Cash network, and its derivation paths are defined for that chain. Users interested in other coins should look at separate wallets built for those networks.
How to install Bchwallet on Windows
- 1
Download the Windows build
Go to the official GitHub Releases page for the project, which is linked from the source repository at github.com/gcash/bchwallet. Download the Windows zip archive for the latest release. Each archive contains the executable, a README, the license and a sample configuration file.
- 2
Verify the file
Before running anything, compare the SHA-256 checksum of the downloaded zip with the value published on the release page. In PowerShell you can run Get-FileHash followed by the file path. If the hashes do not match, delete the file and download it again. If signatures are provided, verify them as well.
- 3
Extract the archive
Unzip the archive into a dedicated folder, for example C:\Tools\bchwallet. Keeping the files in a separate location makes updates and rollbacks easier, and it keeps your configuration file in a predictable place.
- 4
Review the configuration
Open the sample configuration file and read the comments. Set the network you intend to use, the data directory and the RPC settings. Start on testnet if you are learning, and do not expose the RPC port to the internet.
-
Start the daemon
Open Command Prompt or PowerShell in the extracted folder and run the executable with your configuration file. Watch the console output for errors about ports, permissions or missing files, and resolve them before continuing.
System requirements
- Windows with a 64-bit processor, as the release is distributed as a standard executable archive
- Sufficient free disk space for the blockchain data on the network you choose
- A stable internet connection to synchronize with the network
How to use Bchwallet
Bchwallet has no graphical interface, so day-to-day use happens through configuration files and RPC calls. Once the daemon is running and synchronized, you interact with it from another program or from a command-line client that can send JSON-RPC requests.
A typical first session looks like this:
- Start the daemon on testnet using your configuration file, and wait until it reports that synchronization is complete.
- Create or unlock a wallet, following the prompts shown in the console or the documentation for your release.
- Request a new receiving address through the RPC interface, and confirm that the address starts with the expected prefix for the network.
- Send a small test amount from a testnet faucet or another testnet wallet to that address, and check that the balance updates.
- Repeat the process on mainnet only after you understand the derivation path, backup procedure and RPC security settings.
Pros & cons
- Free and released under the permissive ISC license
- Open source code that can be audited and modified
- Prebuilt Windows archives with a README and sample configuration
- Separate derivation paths for mainnet, testnet, regtest and simnet
- RPC interface largely compatible with Bitcoin Core conventions
- Written in Go, a language well suited to network services
- No graphical interface, so it is unsuitable for casual users
- Documentation and setup assume familiarity with the command line
- The gRPC server is marked experimental
- Requires careful key and seed management, since mistakes can be irreversible
- Focused on Bitcoin Cash, so it does not cover other coins
Is Bchwallet safe?
Bchwallet handles private keys and real funds, so treat installation with care. Download the software only from the official GitHub repository or its Releases page. Do not use copies offered on third-party download sites, forums or file-sharing services, since these may be modified.
Always verify the SHA-256 checksum or signature of the archive before running it. Never type or paste your seed phrase into a website, a chat window or any tool you have not personally verified. Store your seed backup offline, in more than one safe location. Restrict RPC access to localhost or a trusted network, because anyone who can reach the RPC port may be able to control the wallet. Check the release date on the repository before relying on a version for real money.
- Official source only. Download from github.com/gcash/bchwallet. 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
Bchwallet differs from most options in this catalog in its audience and architecture. Electron Cash is a desktop wallet with a graphical interface aimed at everyday Bitcoin Cash users, while Bchwallet is a headless daemon that other programs control. If you want to send payments from a window and see your balance at a glance, Electron Cash is the more practical tool.
Compared with Electrum, which covers Bitcoin with features such as Lightning and hardware wallet support, Bchwallet is narrower in scope but more appropriate for server-side integrations. Wasabi Wallet emphasizes privacy through CoinJoin on Bitcoin, a different goal from Bchwallet's backend role. The right choice depends on whether you need a user-facing app or a programmable service.
Specifications
- Price
- Free
- Type
- Open source
- License
- ISC
- Latest version
- walletdb/v1.0.0
- Last update
- 30 Oct 2026
- Windows support
- Yes (Windows build or installer)
- Source code
- github.com/gcash/bchwallet
Frequently asked questions
Yes. Bchwallet is free and released under the ISC license, which allows you to use, copy and modify the software. There are no purchase costs listed for the program itself. Remember that network transaction fees apply when you send Bitcoin Cash, as they do with any wallet.
No. Bchwallet runs as a background daemon without a built-in graphical window. You control it through configuration files and JSON-RPC or gRPC calls, usually from another program or a command-line client. Users who want a visual interface should consider a desktop wallet like Electron Cash instead.
It can be, provided you download it from the official GitHub Releases page and verify the SHA-256 checksum before running it. Avoid unofficial mirrors. Because the code is open source, the community can review it, but you remain responsible for keeping your seed phrase private and restricting access to the RPC port.
Bchwallet supports mainnet, testnet, regtest and simnet. Each network has its own BIP44 derivation path. Mainnet uses m/44'/145'/0', which is the path to choose if you are unsure. Testnet and regtest use m/44'/1'/0', and simnet uses m/44'/115'/0'. Test networks are useful for practice without risking real coins.
The JSON-RPC server is the legacy interface and is largely compatible with Bitcoin Core, so existing tools may work with few changes. The gRPC server is marked experimental and offers a typed API. For production integrations, the JSON-RPC server is generally the more established choice, though you should confirm current status in the documentation.
No, not if you use the prebuilt Windows archive from the Releases page. Go is needed only if you want to build the software from source yourself. The build instructions mention Go-related setup steps, but those apply to compiling the code, not to running a ready-made executable.
Yes, if you have your seed phrase and install the software with the same derivation path that created the wallet. Install the same or a compatible version on the new machine, restore from the seed, and let the daemon rescan the blockchain. Using a different derivation path will show different addresses and may appear as an empty wallet.
That decision depends on your technical skills and security practices. Bchwallet requires careful backup, access control and regular updates. Many users with significant holdings prefer a hardware wallet or a well-established desktop wallet. Whatever you choose, test with small amounts first and keep your seed phrase offline.
Verdict
Bchwallet is a solid, free and open-source option for developers and operators who need a Bitcoin Cash wallet backend on Windows. It rewards technical care with a transparent codebase and a Bitcoin Core-style RPC interface. It is not a good fit for people who want a simple window to send and receive coins. Before using it with real funds, read the documentation, test on testnet, and confirm the latest release on the official repository.