Jeffrey H. Johnson 8729acba84 multi: Add proper attributions, fixup imports, etc | 3 years ago | |
---|---|---|
.. | ||
chain | 3 years ago | |
cmd | 3 years ago | |
docs | 3 years ago | |
internal | 3 years ago | |
netparams | 3 years ago | |
rpc | 3 years ago | |
snacl | 3 years ago | |
waddrmgr | 3 years ago | |
wallet | 3 years ago | |
walletdb | 3 years ago | |
wtxmgr | 3 years ago | |
README.md | 3 years ago | |
config.go | 3 years ago | |
params.go | 4 years ago | |
pktconv.sh | 4 years ago | |
pktwallet.go | 3 years ago | |
pktwallet_test_license_test.go | 3 years ago | |
rpcserver.go | 3 years ago | |
signal.go | 3 years ago | |
signalsigterm.go | 4 years ago | |
walletsetup.go | 3 years ago |
pktwallet is a daemon handling bitcoin wallet functionality for a single user.
It acts as both an RPC client to pktd
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.
pktwallet 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, pktwallet 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.
pktwallet is not an SPV client and requires a connection to a local or remote
pktd
instance for asynchronous blockchain queries, as well as to receive
notifications over websockets.
Wallet clients can use one of two RPC servers:
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.
The RPC server uses a new API built for pktwallet, but, because the API is
not stable, the server is feature gated behind a user configurations option
(--experimentalrpclisten
). If you a) don't mind applications breaking due
to API changes, b) have issues with the legacy API, or c) need to get
notifications for changes to the wallet, this is the RPC server to use.
The integrated GitHub issue tracker is used for this project.
pktwallet is licensed under the liberal ISC License.