Human Network
  • ☀️Welcome to Human Network
  • Overview
    • What is Human Network? What are Human Keys?
    • Methods and their use cases
      • Deriving keys from low-entropy data
      • Deriving keys from web accounts
      • Provably encrypting to Human Network, and setting custom decryption conditions.
    • FAQ
  • For Operators
    • Register and Run a Human Node
      • Use Keystore for private key encryption
      • Keyshare backup
    • Diagnostics using the Network UI
  • Decentralization
    • Architecture
      • Preventing Collusion
      • Scalability
      • Credit System
    • Mainnets and Testnets
  • Usage Instructions
    • Human Network Credits
    • Making Requests to Human Network
      • OPRF To Derive Keys From Low-Entropy Data
      • PRF to Derive Keys from JWTs
      • Decryption of Provably Encrypted Data
    • Sponsor Requests
Powered by GitBook
On this page
  • Instructions for backing up your keyshare:
  • For accessing the backup:
  1. For Operators
  2. Register and Run a Human Node

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.

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

PreviousUse Keystore for private key encryptionNextDiagnostics using the Network UI

Last updated 17 days ago