How to: Issue a remote start for all your Dash MasterNodes

Hi everyone!

Today I am going to cover a simple yet important step in order to have your Dash Masternodes running. Sometimes when you restart a masternode it goes from Enabled/Online to Missing. In order for it to go back to Enabled and continue getting paid, you need to issue a remote start (from your wallet) to enable it. This also applies to new masternodes that you may have deployed. Do keep in mind that if you are setting up a new masternode, you can issue the command masternode start-missing after 15 confirmations.

Now, in order to remote start your masternodes follow these simple 4 steps:

  1. Open your Dash QT wallet.
  2. Open the debug console.
  3. Unlock your wallet. If you don’t you’ll get an error “Your wallet is locked, passphrase is required (code -1)”
  4. Issue the command masternode start-missing

I like to use masternode list-conf to get an idea of which masternodes are online/enabled and which ones are not. If you call the command you’ll get a json file like this one:

{
“masternode” : {
“alias” : “MasterNode01”,
“address” : “:9999”,
“privateKey” : “”,
“txHash” : “”,
“outputIndex” : “0”,
“status” : “MISSING”
},
“masternode” : {
“alias” : “MasterNode02”,
“address” : “:9999”,
“privateKey” : “”,
“txHash” : “”,
“outputIndex” : “1”,
“status” : “MISSING”
}
}

The important thing here to notice is that the status reads MISSING. After running through the steps mentioned above they should read ENABLED if you execute masternode list-conf again.

Bonus:

You can also start only one of the masternodes only by using start-alias. To learn more about this feature check out: How to: Start a single Masternode with start-alias

You may also like...

Leave a Reply

%d bloggers like this:
Skip to toolbar