A wallet is a lightweight client which connects to a peer to receive balance and transaction history information. It also stores and manages private keys on behalf of the user and can be used to sign and publish transactions with them.
- Make sure you have the new Go modules support enabled:
go install github.com/cruzbit/cruzbit/wallet
wallet application is now in
Note to Microsoft Windows users
This software makes use of ANSI escape codes to provide color and highlighting. Some versions of Microsoft Windows are unable to display these proplerly in its default
cmd.exe utility. If you are experiencing this issue please have a look at https://github.com/microsoft/Terminal. It should resolve that issue.
Basic command line arguments
wallet -walletdb <path to a directory to store wallet data>
- walletdb - This points to a directory on disk to store wallet data including private keys. Keys will be encrypted at-rest using a passphrase you will be prompted to enter.
- peer - Specifies the address of a peer to talk to for balance and transaction history information. It will also publish newly signed transactions to this peer. By default, it connects to
- tlsverify - Verify the TLS certificate of the peer is signed by a recognized CA and the host matches the CN. This is recommended if you're connecting to your client peer node over the open Internet. Your client will need to use the
-tlskeyoptions with a certificate signed by a recognized CA.
- recover - Attempt to recover a corrupt
You should only connect the wallet to a client peer you trust. A bad client can misbehave in all sorts of ways that could confuse your wallet and trick you into making transactions you otherwise wouldn't. You also expose which public keys you control to the peer.
The prompt should be mostly self-documenting. Press Tab to cycle through the menu options.
You can use the
newkey command to generate a public/private key pair. The displayed public key can be used as the
-pubkey argument to the client program.
To backup your private keys, make a copy of your
-walletdb directory after you've exited the
Later, you can restore your keys by simply starting the
wallet and pointing
-walletdb at this directory.