I'm now in the position to start another Masternode. I have been seeing a few different threads on multiple MNs and start many. Does anyone know which is the most up to date and best method?
Thanks oblox. I'm just waiting for some buy orders to go through and then I will give this a try.Import your addresses or send your coins to a newly generated address in the wallet. Create a masternode.conf file in your data directory and format accordingly:
https://github.com/darkcoin/darkcoin/pull/62
It can't get any more straight forward than that link.Can someone make a start-many for dummies like me?
Thanks in advance.
Then I guess I won't be using it! :tongue:It can't get any more straight forward than that link.
Then I guess I won't be using it! :tongue:
I'll stick with the manual method.
Thanks.
Not using the start-many/start-alias commands and having an individual wallet and config file for each masternode.What's the manual method Tao? Just in case I end up needing it too!
Would that mean new server for each too?Not using the start-many/start-alias commands and having an individual wallet and config file for each masternode.
Import your addresses or send your coins to a newly generated address in the wallet. Create a masternode.conf file in your data directory and format accordingly:
https://github.com/darkcoin/darkcoin/pull/62
#----
addnode=x.x.x.x:9999
addnode=x.x.x.x:9999
addnode=x.x.x.x:9999
addnode=x.x.x.x:9999
rpcuser=my_user_name
rpcpassword=my_really_long_password
rpcallowip=127.0.0.1
listen=0
server=1
daemon=1
masternode=0
logtimestamps=1
maxconnections=256
mn1 127.0.0.2:19999 93HaYBVUCYjEMeeH1Y4sBGLALQZE1Yc1K64xiqgX37tGBDQL8Xg 2bcd3c84c84f87eaa86e4e56834c92927a07f9e18718810b92e0d0324456a67c 0
mn2 127.0.0.3:19999 93WaAb3htPJEV8E9aQcN23Jt97bPex7YvWfgMDTUdWJvzmrMqey aa9f1034d973377a5e733272c3d0eced1de22555ad45d6b24abadff8087948d4 0
mn3 127.0.0.4:19999 92Da1aYg6sbenP6uwskJgEY2XWB5LwJ7bXRqc3UPeShtHWJDjDv db478e78e3aefaa8c12d12ddd0aeace48c3b451a8b41c570d0ee375e2a02dfd9 1
#--------------------
The start-many/start-alias goes by itself in the masternode.conf file as stated above. It does not go into your darkcoin.conf.RE: The format in the link referenced. I'm still not clear on what the entire darkcoin.conf file should look like. Does this look correct?
Unique IPv4 address, yes. That doesn't change by using the start-many. You still need unique IPv4 addresses, usually a new VPS instance per masternode unless your provider allows multiple IPv4 addresses per instance.Would that mean new server for each too?
Your config file looks good, the tx id and output values match up. To clarify, this masternode.conf file resides locally, not remotely on the masternodes, correct? Also, your wallet that you are loading already has the addresses of the masternodes: in this case, XrAT6jpfWkqHkbChVgj16y86T8VtPaCELj and XxHoRZrK7YTeiXE7XvGNVRajy3ccHCah9Goblox, I setup the masternode.conf file as noted in pull 62. When I enter the console I get 'started 0, failed 0'. The masternode list-conf command returns blank spaces.
mn1 108.61.171.xx:9999 7rT..............................dL4 2489e6368a1496ca215db4a0f71473a3bf9c990d25e061091311445ec8e031c3 0
mn2 108.61.251.xx:9999 7s.................................956 bb3eb95bb7b422bd5079b539f77e1ba02f799162d842efd97a81a87883ee3fdd 0
<alias> <PUBIP> <pirvkey> <blockchain transaction> <transaction index>
When I open the receiving addresses it states "0 First masternode" and "0 Second masternode".
Also, in my darkcoin.conf if I set 'masternode=0' then everything would reside in one wallet and can use darksend?
Thanks much.
It needs to be in the data folder, not necessarily where the executable is.I had fat-fingered masternode.conf file name, so list-conf showed up as blank. Yes, the file is local and in the same directory as darkcoin-qt, etc...
You do bring up a good point about mixing wallets. So now the question becomes if my merged wallet states 2008.5434 DRK for both masternodes I would use coin-control to manage the sending from individual wallets.
Are there any known problems about issuing a start-many command if some of the masternodes are already started? I seem to recall reading about this way back when, but couldn't turn up any info with a search.
I've started on fully synced remotes before.At the moment it doesn't seem to work if the remote MN's are already fully synced and have the MN list. A workaround for that currently is to start the MN's then immediately issue the start-many command from the local wallet.