NEM-tools: Automated restart of delegated harvesting

EM-tools: Automated restart of delegated harvesting

marc0o (35) in nem, first appeared on steemit


If you are currently not familiar with harvesting, delegated harvesting or the NEM-blockchain in general I suggest you to read these articles first:

The “problem” with delegated harvesting

Everybody who makes use of delegated harvesting on the NEM-blockchain is facing the same headaches:

  • delegated harvesting stops when the node you are harvesting on is getting rebooted for some reason
  • you need to manually search for a node with free slots (can be frustrating using NanoWallet)
  • maybe you are on vacation and you cannot afford to restart harvesting
    • you miss the chance to harvest new blocks

Solution provides a service that performs this task for you automatically. When you register for automated restart of delegated harvesting the service will check every 5 minutes whether delegated harvesting for your account is still active or not.

If the node your remote account used to harvest was rebootet or harvesting stopped for some other reason the service will detect this and automatically search for a new node with free slots. If delegated harvesting was successfully restarted you will receive an e-mail with respective information.


The service needs the private key of your delegated account in order to be able to automatically restart delegated harvesting.

  • your delegated private key will be stored encrypted in a database (and can only be decrypted with a secret-key that is stored as environment-variable)
  • in theory it isn’t problematic to publish the private key of your delegated account since your delegated account doesn’t store any value in form of mosaics (XEM or others)


Well you noticed that it shouldn’t be a problem to give out the private key of your delegated account, right? So why should there be cautions to use the service?

NEM is rewarding people by calculating their PoI (read more) and the higher someones importance score is, the higher is his/her chance to harvest new blocks.

You have to be aware of that the more people use this service, the higher will be the attraction for hackers trying to collect and decrypt these encrypted private keys of the delegated accounts stored in the database. Although I tried my best to ensure that this service cannot be compromised by hackers, I cannot guarantee that someone is able to reveal the private keys.

What could happen if a hacker is able to reveal all private keys stored in the database?

  • the hacker would be able to stop harvesting for all accounts and so increase his own “real” PoI because all of the people using this service would not be able to harvest new blocks if he/she stops delegated harvesting for all of you
  • he/she could NOT access the funds (mosaics) that are stored on your main-account
  • worst case scenario would be that everyone who used this service would have to create a new account/wallet, transfer his/her funds to a new account and activate delegated harvesting again
    • correct me if I am wrong with this assumption (!)
    • I am open for any discussion about this topic 🙂
    • for sure they would have to wait again that they have a minimum of 10.000 XEM vested (calculate vested XEM)

Ok I have read enough, now tell me what I have to do!

You need to go click here:

You have to fill in 3 entries in the given formular:

  1. your e-mail address
    • needed to confirm (or delete) your subscription
  2. the public key of your delegated account
    • open NanoWallet
    • click on “Services”
    • click on “Manage delegated account”
    • click on “show delegated account keys”
  3. the private key of your delegated account
    -> enter the password of your wallet below the delegated public key and click on the “plus”-sign (afterwards the private key of your delegated account which is needed to restart harvesting is shown)

Further steps

  1. You will receive an e-mail and need to confirm your request
  2. You will receive an e-mail every time the service of nem-tools restarts delegated harvesting for you
    if there occured an error while restarting delegated harvesting for some reason


  • in order to be able to see in NanoWallet whether harvesting is really active you need to manually set the IP/hostname you received via mail as custom node to check against
    • many people get confused by this
    • this is necessary because the NanoWallet doesn’t know on which node the service of nem-tools started harvesting on
    • if you do not change this manually in NanoWallet delegated harvesting may seem to be inactive although it is active
  • If you want to unsubscribe from this service you can click on the link provided in the e-mail you receive
    • at this moment all of your provided data will be deleted immediately from the database!

Questions, doubts, suggestions?

Feel free to comment this entry or participate in the thread of the official NEM-forum:

You like this service?

Do not forget to upvote and feel free to send me some XEM or other mosaics 😉


You may also like...