dcrwallet is a daemon handling Decred wallet functionality. All interaction with the wallet is performed over RPC.
Public and private keys are derived using the hierarchical
deterministic format described by
Unencrypted private keys are not supported and are never written to
disk. dcrwallet uses the
m/44'/<coin type>'/<account>'/<branch>/<address index>
HD path for all derived addresses, as described by
Due to the sensitive nature of public data in a BIP0032 wallet, dcrwallet 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.
dcrwallet provides two modes of operation to connect to the Decred
network. The first (and default) is to communicate with a single
dcrd instance using JSON-RPC. The second is a
privacy-preserving Simplified Payment Verification (SPV) mode (enabled
--spv flag) where the wallet connects either to specified
--spvconnect) or peers discovered from seeders and other
peers. Both modes can be switched between with just a restart of the
wallet. It is advised to avoid SPV mode for heavily-used wallets
which require downloading most blocks regardless.
Not all functionality is available when running in SPV mode. Some of these features may become available in future versions, but only if a consensus vote passes to activate the required changes. Currently, the following features are disabled or unavailable to SPV wallets:
Revoking tickets before expiry
Determining exact number of live and missed tickets (as opposed to simply unspent).
Wallet clients interact with the wallet using one of two RPC servers:
A JSON-RPC server inspired by the Bitcoin Core rpc server
The JSON-RPC server exists to ease the migration of wallet applications from Core, 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 as long as a username and password are provided.
A gRPC server
The gRPC server uses a new API built for dcrwallet, but the API is not stabilized. This server is enabled by default and may be disabled with the config option
--nogrpc. If you don't mind applications breaking due to API changes, don't want to deal with issues of the JSON-RPC API, or need notifications for changes to the wallet, this is the RPC server to use. The gRPC server is documented here.
Installation and updating
Binary releases are provided for common operating systems and architectures:
Build from source (all platforms)
Building or updating from source requires the following build dependencies:
Go 1.13 or 1.14
Installation instructions can be found here: https://golang.org/doc/install. It is recommended to add
PATHat this point.
To build from a local repo, run
go install in the repo's root directory.
Module builds are required. When working with a source tree under
$GOPATH/src, set the
dcrwalletexecutable will be installed to
%USERPROFILE%\goon Windows) if unset.
go get command can also be used to fetch sources, build, and install
through a single command, without needing to clone the repo. While outside of
any module (
go env GOMOD prints an empty newline), run:
GO111MODULE=on go get decred.org/dcrwallet
An optional version, branch, or tag may be appended following a
after the package name. The implicit default is to build
@latest, which is
the latest semantic version tag. Building
@master will build the latest
development version. See
go help module-get for more details.
The following instructions detail how to get started with dcrwallet connecting
to a localhost dcrd. Commands should be run in
cmd.exe or PowerShell on
Windows, or any terminal emulator on *nix.
- Run the following command to start dcrd:
dcrd -u rpcuser -P rpcpass
- Run the following command to create a wallet:
dcrwallet -u rpcuser -P rpcpass --create
- Run the following command to start dcrwallet:
dcrwallet -u rpcuser -P rpcpass
If everything appears to be working, it is recommended at this point to copy the sample dcrd and dcrwallet configurations and update with your RPC username and password.
PowerShell (Installed from source):
PS> cp $env:GOPATH\src\github.com\decred\dcrd\sample-dcrd.conf $env:LOCALAPPDATA\Dcrd\dcrd.conf PS> cp $env:GOPATH\src\github.com\decred\dcrwallet\sample-dcrwallet.conf $env:LOCALAPPDATA\Dcrwallet\dcrwallet.conf PS> $editor $env:LOCALAPPDATA\Dcrd\dcrd.conf PS> $editor $env:LOCALAPPDATA\Dcrwallet\dcrwallet.conf
Linux/BSD/POSIX (Installed from source):
$ cp $GOPATH/src/github.com/decred/dcrd/sample-dcrd.conf ~/.dcrd/dcrd.conf $ cp $GOPATH/src/github.com/decred/dcrwallet/sample-dcrwallet.conf ~/.dcrwallet/dcrwallet.conf $ $EDITOR ~/.dcrd/dcrd.conf $ $EDITOR ~/.dcrwallet/dcrwallet.conf
The integrated github issue tracker is used for this project.
dcrwallet is licensed under the liberal ISC License.