• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Reuben's Start Multiple Masternodes from One Wallet Guide (start-many)

This has been rebranded.

For the command masternode outputs it's a bit hard to tell which output is for which output if you made several masternode sends through the same wallet though.
 
Last edited by a moderator:
UdjinM6 said:
masternodeprivkey is not tied to MN address until you place it in local and remote config and issue masternode start (or start-many) command. It's just a kind of "communication key" so it's not tied to anything until you start this "communication".
Click to expand...

So just to be clear! If I understand correctly, I can use masternode Genkey from the same wallet multiple times and it will continue to generate random keys. At which point all that is really important is that both the key in the masternode.conf assigned to each masternode matches the dash.conf on remote machines?
 
Darkuopm said:
So just to be clear! If I understand correctly, I can use masternode Genkey from the same wallet multiple times and it will continue to generate random keys. At which point all that is really important is that both the key in the masternode.conf assigned to each masternode matches the dash.conf on remote machines?
Click to expand...

Exactly.
 
This is how my remote dash.conf looks like on two masternodes on the same server:

Masternode 1
---------------------------------------
#----
rpcuser=xxxxx
rpcpassword=xxxxxx
rpcallowip=127.0.0.1
masternodeaddr=my external ip:9999
bind=127.0.0.2
bind=my external ip
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=200
#--------------------
# change ami_public_ip to public ip address which you connected by ssh
externalip=my external ip
#---------------------
#------------
masternode=1
addnode=23.23.186.131
#----------
masternodeprivkey=xxxxxxxxxxxxxxxxxxxxxxxxxx

---------------------------------------------------------------------------------

Masternode 2

#----
rpcuser=xxxxxxxxxxxxxx
rpcpassword=xxxxxxxxxx
rpcallowip=127.0.0.1
rpcport=8003
masternodeaddr=my external ip:9999
bind=127.0.0.4
bind=my external ip
listen=1
server=1
daemon=1
logtimestamps=1
maxconnections=200
#--------------------
# change ami_public_ip to public ip address which you connected by ssh
externalip=my external ip
#---------------------
#------------
masternode=1
addnode=23.23.186.131
#----------
masternodeprivkey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
 
It´s a VPS with 1 core cpu, 512mb ram, 2gb swap and 20gb disk. 4 public IP.

It swaps around 200-400mb but it was really stable with 0.11.1.26. With the new version the dashd-daemon seems to crash quite often. I hope for a quick fix soon.
 
Easy questions:

- I assume we still need more than 1 IP, right? I mean, we also have to follow guides to have more than 1 IP from a VPS :)
- In order to work, i assume that we should launch dash -masternode.conf via command, right?
 
I have question regarding the index numbers. A friend was already running two MN successfully (VPS). The indexes were "1", and "0". "This was verifiable via the "masternode outputs" command. Then, we went through the procedure to add one more node. Now, when the masternode outputs command is run he sees this:
{
"asdfasdfasdf" : "1",
"asdfdaffdas" : "0",
"aadsfdfasas" : "0"
}
(transactions are symbolic, obviously)
Why would he have two "0"s listed?

Background:
  • The first "1" and "0" were already running MN.
  • The third index "0" was "masternode keygen"'d while the other MNs were running.
  • The 1000dash are in a third address, Mn1 and Mn2 were in "getaccountaddress" 0 and 1 respectively. Now when I run "getaccountaddress" 0 (or 1) it lists a different address than the MN addresses. Why would this change? Does it matter?
  • I notice that the index list goes from high to low (1,0,0). Is it possible that the third index would have been "-1" which is not allowed, so the programming changed it to "0"?
  • Would I need to "Masternode stop-many" and then restart them to get them to index right?
Thanks in advance!
 
paperThin said:
I have question regarding the index numbers. A friend was already running two MN successfully (VPS). The indexes were "1", and "0". "This was verifiable via the "masternode outputs" command. Then, we went through the procedure to add one more node. Now, when the masternode outputs command is run he sees this:
{
"asdfasdfasdf" : "1",
"asdfdaffdas" : "0",
"aadsfdfasas" : "0"
}
(transactions are symbolic, obviously)
Why would he have two "0"s listed?

Background:
  • The first "1" and "0" were already running MN.
  • The third index "0" was "masternode keygen"'d while the other MNs were running.
  • The 1000dash are in a third address, Mn1 and Mn2 were in "getaccountaddress" 0 and 1 respectively. Now when I run "getaccountaddress" 0 (or 1) it lists a different address than the MN addresses. Why would this change? Does it matter?
  • I notice that the index list goes from high to low (1,0,0). Is it possible that the third index would have been "-1" which is not allowed, so the programming changed it to "0"?
  • Would I need to "Masternode stop-many" and then restart them to get them to index right?
Thanks in advance!
Click to expand...
There is no connection between getaccountaddress and indexes or counting from high to low. These are just indexes of some unspent 1000 DASH outputs of corresponding txes.
Just look for outputs section in block explorer to verify that. Some random example from block explorer I can find quite fast: masternode outputs for this http://explorer.darkcoin.io/tx/706291a982a74969c4b4deb207849b522a6b1934551a7fe821f827041341213d#o0 would be
"706291a982a74969c4b4deb207849b522a6b1934551a7fe821f827041341213d" : "0"
and for this http://explorer.darkcoin.io/tx/8489a0965f04ab5fbb73a65891d89c634eafad724f1d8a0e90fae6860f195ce4#o1 would be
"8489a0965f04ab5fbb73a65891d89c634eafad724f1d8a0e90fae6860f195ce4" : "1"
 
Ahhh. Thank you UdjinM6! The index is not ordered from my wallet, but rather the index of the transaction! Got it. So multiple "0" in my masternode.conf is not a problem.

I will let you know how it goes...
 
risinhigher said:
or more so the question should be .. where do i put the masternode.conf file ?
Click to expand...
If your dash is set up as standard on a windows machine then yuo put your masternode.conf file in users/"your user name"/AppData/Roaming/Dash
along with your dash.conf

It might also be worth mentioning that I didnt change anything in my dash.conf file on my remote setup
 
EDIT: solved.

As non-expert user trying to get into this, making life easier for newcomers, may i point out a pair of suggestions in the written form?
 
Last edited by a moderator:
Can I donate to more than one address? I mean, can i, in my masternode.conf file, do this?

masternode start-alias YOURMASTERNODEALIAS YOURWALLETPASSWORD DONATIONADDRESS1:10 DONATIONADDRESS2:90

So in other words, have one donation go to the foundation and the other one go to my daily wallet?
 
TanteStefana said:
Can I donate to more than one address? I mean, can i, in my masternode.conf file, do this?

masternode start-alias YOURMASTERNODEALIAS YOURWALLETPASSWORD DONATIONADDRESS1:10 DONATIONADDRESS2:90

So in other words, have one donation go to the foundation and the other one go to my daily wallet?
Click to expand...
Nope. Initial message (dsee) is capable of carrying only one donation address now.
 
You must log in or register to reply here.
Back
Top