This document illustrates several maintenance events including:
- Lost node keys (Remote, VRF, Voting)
- Unlink your account keys
- Link your account
- Recover voting keys
- Re-use keys for harvesting
In case you have lost any combination of Remote, VRF and/or Voting keys which are linked to your main account, you must first unlink your account.
✅ If you have already unlinked your account, jump here.
This process will cost up to 0.1
of the network currency.
You can unlink your account keys by executing the following command:
yourdlt link -t dual-node --url http://dual-01.dhealth.cloud:3000 --maxFee=100000 --unlink
✅ You can now proceed to the setup of your new container/server.
This process will cost up to 0.1
of the network currency.
You can link your account keys by executing the following command:
yourdlt link -t dual-node --url http://dual-01.dhealth.cloud:3000 --maxFee=100000
If you own an encrypted archive with the voting keys, you can use them to continue/restart harversting with the same accounts.
Uncompress the archive in the /opt/dhealth
folder with unzip votingkeys.zip
. After uncompressing, you can list the files and it should produce an output similar to the following:
$ ls -la votingkeys/
total 48
drwxrwxr-x 2 ubuntu ubuntu 4096 Apr 1 18:24 ./
drwxrwxr-x 9 ubuntu ubuntu 4096 Apr 1 18:28 ../
-rw-rw-r-- 1 ubuntu ubuntu 139 Apr 1 18:24 metadata.yml
-rw------- 1 ubuntu ubuntu 34640 Apr 2 10:19 private_key_tree1.dat
✅ You can verify that you have the correct voting key with cat votingkeys/metadata.yml
which will display the voting public key.
- First stop your node with
yourdlt stop -t dual-node
- Then add the uncompressed voting keys to your node, please make sure any other private_key would not get overwritten.
# first "backup" the active key
$ mv dual-node/nodes/dhealth-full-node/votingkeys dual-node/nodes/dhealth-full-node/bk.votingkeys
# then place in your recovered key
$ mv votingkeys dual-node/nodes/dhealth-full-node/votingkeys
This is it, when you startup your node again, it will be using your recovered voting keys:
$ yourdlt run -t dual-node -d
If you issued the account keys link from a different client application (wallet, CLI), you must use a custom configuration preset to run your node using those keys.
Following is an example custom configuration preset that you can use to harvest with a specific account which was already linked to supplemental keys:
nodes:
-
host: ''
friendlyName: 'your-awesome-node'
maxUnlockedAccounts: 40
enableDelegatedHarvestersAutoDetection: true
enableAutoHarvesting: true
beneficiaryAddress: INPUT_HERE
mainPrivateKey: INPUT_HERE
remotePrivateKey: INPUT_HERE
vrfPrivateKey: INPUT_HERE