Edit your local Dash masternode.conf file

May 02, 2016

To update your masternode.conf file, you will need a basic text editor. On Windows you can simply use notepad. For the mac, you can use something like Atom, Textmate, or Sublime Text. Atom is probably the easiest to work with, and it is free. We do not recommend using the application TextEdit on the Mac.

If your Dash wallet is running, it is good practice to shut it down before editing the masternode.conf file.

Find your masternode.conf file

Go to your Dash data directory.

Mac

Default Location: /Users/[username]/Library/Application Support/Dash/

From the Mac finder select Go => Go to Folder... and type in your path.

Edit your local Dash masternode.conf file

Edit your local Dash masternode.conf file

Windows

Default Location: C:\Users\[username]\AppData\Roaming\Dash\

From Windows Start menu type in %appdata% and click the Roaming folder. From there you should see the Dash data directory.

Edit your local Dash masternode.conf file

Edit your local Dash masternode.conf file

In the examples above, replace [username] with the username you used to login to your computer.

Open the masternode.conf file (not dash.conf) with the text editor of your choice.

Get your masternode configuration string(s)

When you commission a node with the Node40 Setup Wizard, your masternode configuration string will be displayed in the Server Configuration section.

Edit your local Dash masternode.conf file

Alternatively, you can find all of your configuration strings by going to the Commissioned Nodes page in Node40. Select Commissioned Nodes under your email address in the upper right corner at Node40.

Edit your local Dash masternode.conf file

To view all of your masternode.conf line items, click the Show masternode.conf line items button.

Update your masternode.conf file.

Paste the configuration string(s) from the Setup Wizard or the Commissioned Nodes page into your masternode.conf file. Paste the string into the last line of your file. Note that you can change the alias to something more meaningful to you. Like moms_node or Node40_001 as used in this example.

Edit your local Dash masternode.conf file Default empty masternode.conf file

Edit your local Dash masternode.conf file Updated masternode.conf file

Your masternode.conf file may already contain line items with # as the first item in the line. These lines are comments and can be left in the file.

Save your masternode.conf file and open your Dash QT Core wallet. Allow the wallet to completely synchronize with the network.

From the Settings menu, select Unlock Wallet....

From the Tools menu select Debug Console.

You can confirm the masternode.conf file is being read correctly by opening the Debug Console and issuing the command masternode list-conf. You should see the information for each of your masternodes output to the screen.

Example output:

{
    "masternode" : {
        "alias" : "Node40_001",
        "address" : "52.202.189.56:9999",
        "privateKey" : "7rrkZ6Dptt4rqH41kjus7Krs5AneWWrckiZNxmx2GeC3RV7oFUA",
        "txHash" : "001650283a6ccc08415c5fe1f614264479d66a455bf707f778240335214c6fef",
        "outputIndex" : "1",
        "status" : "MISSING"
    }
}

If any of your nodes show a status of MISSING you should issue the command masternode start-missing from the Debug Console.

Example output:

{
  "overall" : "Successfully started 1 masternodes, failed to start 0, total 1",
  "detail" : {
    "status" : {
      "alias" : "Node40_001",
      "result" : "succesful"
  }
}