Masternode start-many Guide The command Masternode start-many is still under development and might not function as good as the regular setup! Running and updating several Masternodes means you must have a separate wallet containing the 1000 DRK for each node. All wallets and their data folders have to be synchronized with the network in order to run properly. The latest release 10.16.15 supports the option to run a number of nodes from a single wallet with one data folder. Running the nodes from that wallet and starting the nodes with one command is much easier. We will still need a separate DRK address (with 1000 DRK) per node in the new wallet. This is not a beginner guide and some knowledge in setup and running a masternode is needed. How it works Was explained by UdjinM6 "https://darkcointalk.org/threads/v10-16-onyx-v2.2982/page-16#post-29792 Wallet just reads IP + masternodeprivatekey from single line in masternode conf and takes the first vin that is available (contains unspent 1000 DRK) and use it to start masternode. Then it repeats until the end of the file. So there is no right or wrong public key for the ip address because there is no column for vin or corresponding public key in masternode.conf - they are not tied now." Let's Start! 1. We have two setup options: a. New wallet setup - creation on new addresses and DRK transfer. b. Consolidation - transfer several "old" wallets into one new wallet. 2. darkcoin.conf and masternode.conf setup. a. New wallet setup Create a new address per Masternode and encrypt the wallet. IMPORTENT! Please backup the wallet now. Always backup the wallet BEFORE transferring any DRK! Transfer 1000 DRK to each newly created address. b. Consolidation of old wallets setup Get the private keys of all "old" addresses (Hot wallets). Command : "dumpprivkey <your-old-Darkcoin-address-here>" Install a new wallet (one address zero DRK). If you encrypted your wallet, you will need to unlock it before you import the keys. Command: "walletpassphrase <passphrase> <timeout>" Now on the new wallet "importprivkey <my priv key>" be patient might take some time to rescan the blockchain and import all the previous transactions of that address. All newly imported address end up in the "Addresses" Tab. Right mouse click the address and edit its Label (Ex. MN1, MN2 etc). Leave the Address field as is! Click "OK", that will move the address to the "Receive" Tab. After all addresses were imported encrypt the wallet and create a backup! Keep a backup of ALL "old" wallets for security. darkcoin.conf setup Local darkcoin.conf masternodeprivkey was generated from Local wallet and used just to get the client to load. (qt refuses to load without masternodeprivkey when masternode=1) Code: rpcuser=your-user-name rpcpassword=your-long-password rpcallowip=127.0.0.1 listen=0 server=1 daemon=1 logtimestamps=1 masternode=1 masternodeprivkey=7aaaaaaaaaaaaaaaaaaa Generated from LOCAL wallet! addnode=126.96.36.199 Remote darkcoin.conf masternodeprivkey was generated from Local wallet. Code: rpcuser=your-user-name rpcpassword=your-long-password rpcallowip=127.0.0.1 listen=1 server=1 daemon=1 logtimestamps=1 maxconnections=256 masternode=1 masternodeprivkey=7bbbbbbbbbbbbbbbbbbb Generated from LOCAL wallet! addnode=188.8.131.52 masternode.conf setup Location of masternode.conf: under same directory as darkcoin-qt.exe Code: 184.108.40.206:9999 7bbbbbbbbbbbbbbbbbbb Generated from LOCAL wallet! Please note that the masternodeprivkey of the remote darkcoin.conf and the masternode.conf must be identical! Exaple of masternode.conf (5 nodes) Code: 220.127.116.11:9999 7bbbbbbbbbbbbbbbbbbb 18.104.22.168:9999 7ccccccccccccccccccccc 22.214.171.124:9999 7ddddddddddddddddddd 126.96.36.199:9999 7eeeeeeeeeeeeeeeeeee 188.8.131.52:9999 7ffffffffffffffffffff A new masternodeprivkey must be generated for each Masternode. The masternodeprivkey is identical to the one in the remote darkcoin.conf of that IP. How to start the Masternodes masternode start-many since the wallet doesn't confirm the start, the best way is to grep and check if your IP's are on the list. I'm running a script that greps all the IP's to check if they are on the list. Currently there is no "stop-many" and stopping the nodes is an issue. Since there are no documentation on start-many, it was trial and error for me. would love to get input from members that are using start-many so we could correct and update this guide. Good Luck!