sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-23 19:12:47 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge bitcoin/bitcoin#22523: Document about wallet backup and restoration

Browse Source 
ce4e90629ed70f4d45906d7e79563b2f7ad6493e Document about wallet backup and restoration (lsilva01)

Pull request description:

  This PR adds a document about backing up and restoring the Bitcoin Core wallet as suggested in the issue https://github.com/bitcoin/bitcoin/issues/20149 .

ACKs for top commit:
  achow101:
    re-ACK ce4e90629ed70f4d45906d7e79563b2f7ad6493e
  prayank23:
    reACK ce4e90629e
  meshcollider:
    re-ACK ce4e90629ed70f4d45906d7e79563b2f7ad6493e

Tree-SHA512: 68881fc1d81ff27cb59b891e6d422e303844a751afd9f4699f7ae505f204452afe9496c9be915ba94a7045f3cf3eaeb2af0e42ff2a12b4c77ef1f71a9de4faad
This commit is contained in:
Samuel Dobson 2021-08-16 01:59:08 +12:00 committed by PastaPastaPasta
parent 38b9074275
commit 5bd334a33b
1 changed files with 125 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

125
doc/managing-wallets.md Normal file
View File

@ -0,0 +1,125 @@
# Managing the Wallet
## 1. Backing Up and Restoring The Wallet
### 1.1 Creating the Wallet
Since version 0.21, Dash Core no longer has a default wallet.
Wallets can be created with the `createwallet` RPC or with the `Create wallet` GUI menu item.
In the GUI, the `Create a new wallet` button is displayed on the main screen when there is no wallet loaded. Alternatively, there is the option `File` ->`Create wallet`.
The following command, for example, creates a descriptor wallet. More information about this command may be found by running `dash-cli help createwallet`.
```
$ dash-cli -named createwallet wallet_name="wallet-01" descriptors=true
```
The `descriptors` parameter can be omitted if the intention is to create a legacy wallet. For now, the default type is the legacy wallet, but that is expected to change in a future release.
By default, wallets are created in the `wallets` folder of the data directory, which varies by operating system, as shown below. The user can change the default by using the `-datadir` or `-walletdir` initialization parameters.
| Operating System | Default wallet directory |
| -----------------|:------------------------------------------------------------|
| Linux | `/home/<user>/.dashcore/wallets` |
| Windows | `C:\Users\<user>\AppData\Roaming\DashCore\wallets` |
| macOS | `/Users/<user>/Library/Application Support/DashCore/wallets` |
### 1.2 Encrypting the Wallet
The `wallet.dat` file is not encrypted by default and is, therefore, vulnerable if an attacker gains access to the device where the wallet or the backups are stored.
Wallet encryption may prevent unauthorized access. However, this significantly increases the risk of losing coins due to forgotten passphrases. There is no way to recover a passphrase. This tradeoff should be well thought out by the user.
Wallet encryption may also not protect against more sophisticated attacks. An attacker can, for example, obtain the password by installing a keylogger on the user's machine.
After encrypting the wallet or changing the passphrase, a new backup needs to be created immediately. The reason is that the keypool is flushed after encryption. Any coins received by the new wallet cannot be recovered from the previous backups. HD wallets do not have this issue.
The wallet's private key may be encrypted with the following command:
```
$ dash-cli -rpcwallet="wallet-01" encryptwallet "passphrase"
```
Once encrypted, the passphrase can be changed with the `walletpassphrasechange` command.
```
$ dash-cli -rpcwallet="wallet-01" walletpassphrasechange "oldpassphrase" "newpassphrase"
```
The argument passed to `-rpcwallet` is the name of the wallet to be encrypted.
Only the wallet's private key is encrypted. All other wallet information, such as transactions, is still visible.
The wallet's private key can also be encrypted in the `createwallet` command via the `passphrase` argument:
```
$ dash-cli -named createwallet wallet_name="wallet-01" descriptors=true passphrase="passphrase"
```
Note that if the passphrase is lost, all the coins in the wallet will also be lost forever.
### 1.3 Unlocking the Wallet
If the wallet is encrypted and the user tries any operation related to private keys, such as sending coins, an error message will be displayed.
```
$ dash-cli -rpcwallet="wallet-01" sendtoaddress "tb1qw508d6qejxtdg4y5r3zarvary0c5xw7kxpjzsx" 0.01
error code: -13
error message:
Error: Please enter the wallet passphrase with walletpassphrase first.
```
To unlock the wallet and allow it to run these operations, the `walletpassphrase` RPC is required.
This command takes the passphrase and an argument called `timeout`, which specifies the time in seconds that the wallet decryption key is stored in memory. After this period expires, the user needs to execute this RPC again.
```
$ dash-cli -rpcwallet="wallet-01" walletpassphrase "passphrase" 120
```
In the GUI, there is no specific menu item to unlock the wallet. When the user sends coins, the passphrase will be prompted automatically.
### 1.4 Backing Up the Wallet
To backup the wallet, the `backupwallet` RPC or the `Backup Wallet` GUI menu item must be used to ensure the file is in a safe state when the copy is made.
In the RPC, the destination parameter must include the name of the file. Otherwise, the command will return an error message like "Error: Wallet backup failed!" for descriptor wallets. If it is a legacy wallet, it will be copied and a file will be created with the default file name `wallet.dat`.
```
$ dash-cli -rpcwallet="wallet-01" backupwallet /home/node01/Backups/backup-01.dat
```
In the GUI, the wallet is selected in the `Wallet` drop-down list in the upper right corner. If this list is not present, the wallet can be loaded in `File` ->`Open wallet` if necessary. Then, the backup can be done in `File` -> `Backup Wallet...`.
This backup file can be stored on one or multiple offline devices, which must be reliable enough to work in an emergency and be malware free. Backup files can be regularly tested to avoid problems in the future.
If the computer has malware, it can compromise the wallet when recovering the backup file. One way to minimize this is to not connect the backup to an online device.
If both the wallet and all backups are lost for any reason, the coins related to this wallet will become permanently inaccessible.
### 1.5 Backup Frequency
The Dash Core wallet is by default a collection of unrelated private keys. If a non-HD wallet had received funds to an address and then was restored from a backup made before the address was generated, then any funds sent to that address would have been lost because there was no deterministic mechanism to derive the address again.
Dash Core [version 0.12.2](https://github.com/dashpay/dash/blob/master/doc/release-notes/dash/release-notes-0.12.2.md) introduced HD wallets with deterministic key derivation. With HD wallets, users no longer lose funds when restoring old backups because all addresses are derived from the HD wallet seed.
This means that a single backup is enough to recover the coins at any time. It is still recommended to make regular backups (once a week) or after a significant number of new transactions to maintain the metadata, such as labels. Metadata cannot be retrieved from a blockchain rescan, so if the backup is too old, the metadata will be lost forever.
Non-HD wallets must be backed up every 1000 keys used since the previous backup, or even more often to maintain the metadata.
### 1.6 Restoring the Wallet From a Backup
To restore a wallet, the `restorewallet` RPC must be used.
```
$ dash-cli restorewallet "restored-wallet" /home/node01/Backups/backup-01.dat
```
After that, `getwalletinfo` can be used to check if the wallet has been fully restored.
```
$ dash-cli -rpcwallet="restored-wallet" getwalletinfo
```
The restored wallet can also be loaded in the GUI via `File` ->`Open wallet`.