Greetings @rishi556 ! Thank you very much for sharing this post. I have a question, I hope you can help me.
Find the private active_key using your preferred choice. If your private active key is 5KNrHHigj3PRurkm5moaV1XM3gWGrDZJJZCgPRL2FpBLjWy1obg you'd import it by typing in import_key 5KNrHHigj3PRurkm5moaV1XM3gWGrDZJJZCgPRL2FpBLjWy1obg
By this, do you mean the private active key of the witness account, or the same one generated in the previous step, when we did "suggest_brain_key"?
The witness already has more than 24 hours synchronized and printing the lines that I indicate in the image
And he's active on the witness list.
Do you think everything is fine?
You'll want to import your private active key first to be able to broadcast the operation to enable your witness, I also recommend importing the key from
suggest_brain_keyas some CLI commands use it(witness_update actions I believe is what they are called).That's normal. It's just how your node is spending most of its, time, it's mostly idle, which is good since it's not getting overloaded.
As long as your key is correct in the config.ini(most common issue I've seen people do), you are good to go. Now go out there and get more votes, best of luck to you.
I already imported the private active key of the witness project, I have not imported the ones I generated with suggest_brain_key, although I did write it in the config.ini file. So import the one from suggest_brain_key, and everything is ready, or is it not necessary now?
Friend, thank you very much for your prompt response, that is very valuable.
Not necessary if you aren't going to use the CLI. I honestly never use the CLI anymore, it was basically only used for enable/disable which worked with just the active key, then I've used ausbit's site to manage which key is active or enabling/disabling ever since. Check it out here: https://hive.ausbit.dev/witnesss
Brilliant! thank you so much!!!