ltcwallet
ltcwallet is a daemon handling litecoin wallet functionality for a
single user. It acts as both an RPC client to ltcd 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. ltcwallet 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,
ltcwallet 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.
ltcwallet is not an SPV client and requires connecting to a local or
remote ltcd instance for asynchronous blockchain queries and
notifications over websockets. Full ltcd installation instructions
can be found here. An alternative
SPV mode that is compatible with ltcd and Litecoin Core is planned for
a future release.
Wallet clients can use one of two RPC servers:
-
A legacy JSON-RPC server mostly compatible with Litecoin Core
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.
-
An experimental gRPC server
The gRPC server uses a new API built for ltcwallet, 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.
Requirements
Go 1.12 or newer.
Installation and updating
Windows - MSIs Available
Install the latest MSIs available here:
https://github.com/ltcsuite/ltcd/releases
https://github.com/ltcsuite/ltcwallet/releases
Windows/Linux/BSD/POSIX - Build from source
$ go version
$ go env GOROOT GOPATH
NOTE: The GOROOT
and GOPATH
above must not be the same path. It is
recommended that GOPATH
is set to a directory in your home directory such as
~/goprojects
to avoid write permission issues. It is also recommended to add
$GOPATH/bin
to your PATH
at this point.
- Run the following commands to obtain ltcwallet, all dependencies, and install it:
$ cd $GOPATH/src/github.com/ltcsuite/ltcwallet
$ GO111MODULE=on go install -v . ./cmd/...
- ltcwallet (and utilities) will now be installed in
$GOPATH/bin
. If you did
not already add the bin directory to your system path during Go installation,
we recommend you do so now.
Updating
Windows
Install a newer MSI
Linux/BSD/MacOSX/POSIX - Build from Source
- Run the following commands to update ltcd, all dependencies, and install it:
$ cd $GOPATH/src/github.com/ltcsuite/ltcwallet
$ git pull
$ GO111MODULE=on go install -v . ./cmd/...
Getting Started
The following instructions detail how to get started with ltcwallet connecting
to a localhost ltcd. Commands should be run in cmd.exe
or PowerShell on
Windows, or any terminal emulator on *nix.
- Run the following command to start ltcd:
ltcd -u rpcuser -P rpcpass
- Run the following command to create a wallet:
ltcwallet -u rpcuser -P rpcpass --create
- Run the following command to start ltcwallet:
ltcwallet -u rpcuser -P rpcpass
If everything appears to be working, it is recommended at this point to
copy the sample ltcd and ltcwallet configurations and update with your
RPC username and password.
PowerShell (Installed from MSI):
PS> cp "$env:ProgramFiles\ltcd Suite\ltcd\sample-ltcd.conf" $env:LOCALAPPDATA\ltcd\ltcd.conf
PS> cp "$env:ProgramFiles\ltcd Suite\ltcwallet\sample-ltcwallet.conf" $env:LOCALAPPDATA\ltcwallet\ltcwallet.conf
PS> $editor $env:LOCALAPPDATA\ltcd\ltcd.conf
PS> $editor $env:LOCALAPPDATA\ltcwallet\ltcwallet.conf
PowerShell (Installed from source):
PS> cp $env:GOPATH\src\github.com\ltcsuite\ltcd\sample-ltcd.conf $env:LOCALAPPDATA\ltcd\ltcd.conf
PS> cp $env:GOPATH\src\github.com\ltcsuite\ltcwallet\sample-ltcwallet.conf $env:LOCALAPPDATA\ltcwallet\ltcwallet.conf
PS> $editor $env:LOCALAPPDATA\ltcd\ltcd.conf
PS> $editor $env:LOCALAPPDATA\ltcwallet\ltcwallet.conf
Linux/BSD/POSIX (Installed from source):
$ cp $GOPATH/src/github.com/ltcsuite/ltcd/sample-ltcd.conf ~/.ltcd/ltcd.conf
$ cp $GOPATH/src/github.com/ltcsuite/ltcwallet/sample-ltcwallet.conf ~/.ltcwallet/ltcwallet.conf
$ $EDITOR ~/.ltcd/ltcd.conf
$ $EDITOR ~/.ltcwallet/ltcwallet.conf
Issue Tracker
The integrated github issue tracker
is used for this project.
GPG Verification Key
All official release tags are signed by Conformal so users can ensure the code
has not been tampered with and is coming from the ltcsuite 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
License
ltcwallet is licensed under the liberal ISC License.