I wrote up a start-many guide. Can someone here vet it and provide feedback?
https://github.com/perrywoodin/darkcoin-startmany-guide/blob/master/README.md
Multiple Masternodes
- Thread starter calnaughtonjnr
- Start date
I wrote up a start-many guide. Can someone here vet it and provide feedback?
https://github.com/perrywoodin/darkcoin-startmany-guide/blob/master/README.md
TaoOfSatoshi
Well-known member
Thank you for this!
This is the first guide I've seen that makes me confident enough to attempt a start-many.
This dummy finally gets it!
Glad to be a help. The first 6 took me a while, but now I can do the setup in my sleep :wink:
I would start from this step https://github.com/perrywoodin/darkcoin-startmany-guide/blob/master/README.md#create-private-keys as all previous are quite irrelevant to start-many itself
BUT THIS STEP IS WRONG!!
You shouldn't dump mn address privkey, you should take masternodeprivkey from corresponding MN or generate new one by "masternode genkey" and update it on MN too
https://github.com/perrywoodin/dark...ob/master/README.md#get-the-collateral-output
no need to go to explorer, use "masternode outputs" instead
https://github.com/perrywoodin/dark...ternode-details-into-your-masternodeconf-file
not always "0" at the end, use info from "masternode outputs"
https://github.com/perrywoodin/dark...b/master/README.md#edit-the-masternodeprivkey
same as first my note - keep it or use the new one you generated by "masternode genkey" (depends on what you did earlier)
EDIT:
ONCE AGAIN - DO NOT DUMP YOUR PRIVKEY AND DO NOT STORE IT IN masternode.conf
IT'S HIGHLY UNSAFE
Thanks for this. Unfortunately, dumping the priv key works. I'll make sure to update the guide and my nodes to use masternode genkey.
I'm not saying it doesn't work. It does work because "masternode genkey" actually returns you legit privatekey but for some dummy address.
But please hear me - you store private key in masternode.conf and on external server!!! That's just the same as storing 1000 DRK there!
If you did this kind of setup for yourself I would HIGHLY recommend to fix it ASAP.
Yes. I undertand. Fixing now. Thanks again. And I'll update the guide today.
you need masternode genkey and use this key in your remote darkcoin.conf and local masternode.conf but NOT dumpprivkey of the masternode wallet address.
the other thing is that you can use existing wallet where was 1000 input, like old masternode which you started seperatly as a single one. All you need it to clarify the position in the output index in the txid, it can be any number but using fresh wallet it is always 0 than.
the other thing is that you can use existing wallet where was 1000 input, like old masternode which you started seperatly as a single one. All you need it to clarify the position in the output index in the txid, it can be any number but using fresh wallet it is always 0 than.
Ok. Updated my nodes with masternode genkey and updated the guide so others don't make the same mistake I did.
By using the 1000 from an existing wallet, you could then have a wallet that is used solely for the purpose of starting/stopping your MNs. Your coins would then reside in individual MN wallets. Is that right?
That would be nice if you are managing MNs for a group of individuals and you want that group to have a separate wallet.
That makes sense imo.
btw there is no need to delete/move your existing wallet https://github.com/perrywoodin/darkcoin-startmany-guide/blob/master/README.md#create-new-wallet
You can use -wallet cmd line option and easily switch between all wallets you have :wink:
Code:
> darkcoind --help
...
-wallet=<file> Specify wallet file (within data directory) (default: wallet.dat)
...you simply import the privkey on one wallet and than start many, anyway there are different ways to do it but the rule is only one
TaoOfSatoshi
Well-known member
orangecycle
I will wait until you update your guide before attempting. Good time to procrastinate! :wink:
I will wait until you update your guide before attempting. Good time to procrastinate! :wink:
Updated!
Ahh.. Nice! It's getting better and better! Thank you for your efforts!
Few suggestions though:
- use "masternodeprivkey" / "masternode private key" instead of "priv_key" / "private key" / etc where it applies to avoid confusions.
- this part https://github.com/perrywoodin/dark...ternode-details-into-your-masternodeconf-file is a mix of a structure and an example. I would separate one from another.
You can use https://github.com/darkcoin/darkcoin/blob/master/doc/masternode_conf.md as a reference for field names (structure) and example.
PS. Once your guide became quite solid I think it would be a good idea to push it to https://github.com/darkcoin/darkcoin/tree/master/doc as start-many_guide.md or smth like that :wink:
drkrooster
Member
Thanks!
and yes, it is worth mentioning that the key we store in plaintext masternode.conf file is masternodeprivkey which is generated by masternode genkey not the private key that hold 1000DRK.
dumpprivkey is just used to import to our new consolidated wallet with importprivkey
and yes, it is worth mentioning that the key we store in plaintext masternode.conf file is masternodeprivkey which is generated by masternode genkey not the private key that hold 1000DRK.
dumpprivkey is just used to import to our new consolidated wallet with importprivkey
Thanks for the additional suggestions. Keep them coming!
The guide has been updated.
And yes... it would be great to see this end up in the darkcoin repo on github. Let me know how we can make it happen.
Note, I didn't force you to ask me for that :grin::
"ipaddress" -> "ipaddress
ort"To make it end up in darkcoin repo you just have to fork it on github, clone it to your local machine, [create new branch,] put you guide inside of doc folder, add it, commit, push repo back to github and finally create new pull request. Easy
:what::wink:
Note, I didn't force you to ask me for that :grin::
"ipaddress" -> "ipaddress
To make it end up in darkcoin repo you just have to fork it on github, clone it to your local machine, [create new branch,] put you guide inside of doc folder, add it, commit, push repo back to github and finally create new pull request. Easy
This one is for you. https://github.com/perrywoodin/dark...mmit/18a83c495639e8b349f758b4a78327fc0c578581
Ok. I'll have to work on my git skills this weekend.
LOL You made my day with that commit!! :grin::grin::grin: