Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generating Private key auto #136

Open
ImTheDeveloper opened this issue Aug 25, 2018 · 0 comments
Open

Generating Private key auto #136

ImTheDeveloper opened this issue Aug 25, 2018 · 0 comments

Comments

@ImTheDeveloper
Copy link
Contributor

I'm looking at forking the project to add in some code to generate the masternode private key. I'm wondering if the author of the project has given this some thought before and already has a view of where would be sensible to add this.

I've got a couple of thoughts on approaches which briefly breakdown in to the following.

Upon load the script will ask for the n count of nodes you wish to install whether you want to auto-gen or provide the keys upfront.

a. If they say they will provide keys then it will grab each key in turn from them and store temporarily.
b. If they say they want to auto generate then the script will store the selection.

In scenario a, we simply take the keys and replace the placeholders in the config file as we do with ports and IP addresses.

In scenario b, at the end of the script we can use the coins cli to generate the key for each config file and add these in e.g. shekel-cli -conf=/etc/masternodes/jew1/jew.conf masternode genkey

Any issues with this approach?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant