cashwallet is a daemon handling bitcoin cash wallet functionality for a single user. It acts as both an RPC client to gcash and an RPC server for wallet clients and legacy RPC applications.
Public and private keys are derived using the hierarchical
deterministic format described by
BIP0032.
Unencrypted private keys are not supported and are never written to
disk. cashwallet uses the
m/44'/<coin type>'/<account>'/<branch>/<address index>
HD path for all derived addresses, as described by
BIP0044.
Due to the sensitive nature of public data in a BIP0032 wallet, cashwallet provides the option of encrypting not just private keys, but public data as well. This is intended to thwart privacy risks where a wallet file is compromised without exposing all current and future addresses (public keys) managed by the wallet. While access to this information would not allow an attacker to spend or steal coins, it does mean they could track all transactions involving your addresses and therefore know your exact balance. In a future release, public data encryption will extend to transactions as well.
cashwallet is not an SPV client and requires connecting to a local or remote gcash instance for asynchronous blockchain queries and notifications over websockets. Full gcash installation instructions can be found here. An alternative SPV mode that is compatible with gcash and Bitcoin-ABC is planned for a future release.
Wallet clients can use one of two RPC servers:
-
A legacy JSON-RPC server mostly compatible with Bitcoin-ABC
The JSON-RPC server exists to ease the migration of wallet applications from Bitcoin-ABC, but complete compatibility is not guaranteed. Some portions of the API (and especially accounts) have to work differently due to other design decisions (mostly due to BIP0044). However, if you find a compatibility issue and feel that it could be reasonably supported, please report an issue. This server is enabled by default.
-
An experimental gRPC server
The gRPC server uses a new API built for cashwallet, but the API is not stabilized and the server is feature gated behind a config option (
--experimentalrpclisten
). If you don't mind applications breaking due to API changes, don't want to deal with issues of the legacy API, or need notifications for changes to the wallet, this is the RPC server to use. The gRPC server is documented here.
Install the latest MSIs available here:
https://github.com/bcext/gcash/releases
https://github.com/bcext/cashwallet/releases
Building or updating from source requires the following build dependencies:
-
Go 1.5 or 1.6
Installation instructions can be found here: http://golang.org/doc/install. It is recommended to add
$GOPATH/bin
to yourPATH
at this point.Note: If you are using Go 1.5, you must manually enable the vendor experiment by setting the
GO15VENDOREXPERIMENT
environment variable to1
. This step is not required for Go 1.6. -
Glide
Glide is used to manage project dependencies and provide reproducible builds. To install:
go get -u github.com/Masterminds/glide
Unfortunately, the use of glide
prevents a handy tool such as go get
from
automatically downloading, building, and installing the source in a single
command. Instead, the latest project and dependency sources must be first
obtained manually with git
and glide
, and then go
is used to build and
install the project.
Getting the source:
For a first time installation, the project and dependency sources can be
obtained manually with git
and glide
(create directories as needed):
git clone https://github.com/bcext/cashwallet $GOPATH/src/github.com/bcext/cashwallet
cd $GOPATH/src/github.com/bcext/cashwallet
glide install
To update an existing source tree, pull the latest changes and install the matching dependencies:
cd $GOPATH/src/github.com/bcext/cashwallet
git pull
glide install
Building/Installing:
The go
tool is used to build or install (to GOPATH
) the project. Some
example build instructions are provided below (all must run from the cashwallet
project directory).
To build and install cashwallet
and all helper commands (in the cmd
directory) to $GOPATH/bin/
, as well as installing all compiled packages to
$GOPATH/pkg/
(use this if you are unsure which command to run):
go install . ./cmd/...
To build a cashwallet
executable and install it to $GOPATH/bin/
:
go install
To build a cashwallet
executable and place it in the current directory:
go build
The following instructions detail how to get started with cashwallet connecting
to a localhost gcash. Commands should be run in cmd.exe
or PowerShell on
Windows, or any terminal emulator on *nix.
- Run the following command to start gcash:
gcash -u rpcuser -P rpcpass
- Run the following command to create a wallet:
cashwallet -u rpcuser -P rpcpass --create
- Run the following command to start cashwallet:
cashwallet -u rpcuser -P rpcpass
If everything appears to be working, it is recommended at this point to copy the sample gcash and cashwallet configurations and update with your RPC username and password.
PowerShell (Installed from MSI):
PS> cp "$env:ProgramFiles\Bcext\Gcash\sample-gcash.conf" $env:LOCALAPPDATA\Gcash\gcash.conf
PS> cp "$env:ProgramFiles\Bcext\Cashwallet\sample-cashwallet.conf" $env:LOCALAPPDATA\Cashwallet\cashwallet.conf
PS> $editor $env:LOCALAPPDATA\Gcash\gcash.conf
PS> $editor $env:LOCALAPPDATA\Cashwallet\cashwallet.conf
PowerShell (Installed from source):
PS> cp $env:GOPATH\src\github.com\bcext\gcash\sample-gcash.conf $env:LOCALAPPDATA\Gcash\gcash.conf
PS> cp $env:GOPATH\src\github.com\bcext\cashwallet\sample-cashwallet.conf $env:LOCALAPPDATA\Cashwallet\cashwallet.conf
PS> $editor $env:LOCALAPPDATA\Gcash\gcash.conf
PS> $editor $env:LOCALAPPDATA\Cashwallet\cashwallet.conf
Linux/BSD/POSIX (Installed from source):
$ cp $GOPATH/src/github.com/bcext/gcash/sample-gcash.conf ~/.gcash/gcash.conf
$ cp $GOPATH/src/github.com/bcext/cashwallet/sample-cashwallet.conf ~/.cashwallet/cashwallet.conf
$ $EDITOR ~/.gcash/gcash.conf
$ $EDITOR ~/.cashwallet/cashwallet.conf
The integrated github issue tracker is used for this project.
All official release tags are signed by Conformal so users can ensure the code has not been tampered with and is coming from the btcsuite developers. To verify the signature perform the following:
-
Download the public key from the Conformal website at https://opensource.conformal.com/GIT-GPG-KEY-conformal.txt
-
Import the public key into your GPG keyring:
gpg --import GIT-GPG-KEY-conformal.txt
-
Verify the release tag with the following command where
TAG_NAME
is a placeholder for the specific tag:git tag -v TAG_NAME
cashwallet is licensed under the liberal ISC License.