Keyshare backup

For resiliency and consistency of the network, a backup process will be performed at a regular basis. If the team contacts you, please follow the following to perform the backup of your keyshare:

Please select a backup repo outside your node_state/<your_peerID> repo, as this is overwritten at with each new epoch.

You might be asked to perform multiple backups over time, so please add the current date to your backup repo e.g. human_network_backup/<current_date> repo.

Instructions for backing up your keyshare:

• install latest version of openssl

• go to your node_state/<your_peerID> repo (you will find the node_state folder in the present working directory, where the docker-compose.yml file is)

• encrypt your db file by running the following command:

  openssl enc -aes256 -pbkdf2 -in db -out db.aes256

  As prompted password we highly recommend that you use your operator address private key to not overload you with key/password management.

• copy your node_state/<your_peerID> repo to the place you would like to store it (<path>)

  cd ..

  cp -R <your_peerID> <path>

• generate a checksum of your keyshare

  cd <path>/<your_peerID>

  sha512sum db > db.sum

• remove the plaintext version of your db file

  rm db

For accessing the backup:

• go to your backup repo

• decrypt the keyshare

  openssl enc -aes256 -pbkdf2 -d -in db.aes256 -out db

  use the same prompted password as for encryption (your operator private key)

• replace the current node_state/<your_peerID> folder by the backup one

  cd ..

  cp -R <your_peerID> <path>

• verify the checksum

  cd <path>/<your_peerID>

  sha512sum -c db.sum

• remove the encryption of db and checksum

  rm db.aes256

  rm db.sum