EDIT: Updated for the 0.12.0.58 release. Assumes you are simply upgrading and already have a remote masternode running on a Linux 64-bit operating system. Also, I changed the order of the steps to ensure your MN is down for as little time as possible (thus reducing the probability that you will need to manually restart the masternode from your cold wallet)... in previous versions this guide had you stop the MN before it was absolutely necessary. Finally, I have changed some verbiage to improve the clarity of some steps.
Note that dash-cli may not be necessary to replace, but I always replace it just in case something has changed.
Step 1: Once logged into your linux server, identify the location of "dashd" and "dash-cli" - these are the files we aim to replace
Most guides have users place dashd and dash-cli in the main directory while others place them inside a dash directory. No worries, it should be easy to find. Let's take a look at your files. Navigate to the main login directory and determine the location of these files.
You should see a list of files and directories. You will likely see dashd and dash-cli directly here, or there might be some directories for dash in which they reside. If you didn't see dashd or dash-cli here, you will likely see a directory with dash in the name and you can navigate there to take a look.
You should be able to search around and find it easily.
Step 2: Get the version number of your current dashd masternode
This will be useful if you plan to keep copies of your old dashd
Note down the version. You will need that information later.
Step 3: Now we need to get the new files
You should see the file downloading (although you may need to wait a while for it to start). Once it is done, we should be able to see the file. Let's take a look.
Step 4: Now we need to unpack the contents
You should see a bunch of new directories that got created and a couple of dashd files will be among them. For the purposes of this guide, I'm assuming that you require the 64 bit version.
Step 5: Stop your old dashd and move the old binaries to a new name
This example assumes that you were previously running 12.0.57, and really you could name the old dashd and dash-cli whatever you want if you'd like to use a different naming convention than I've suggested below. It is a good idea to keep at least one old copy of an earlier version of dashd around just in case there is a "rollback" or major bug discovered or you get hung up on a later step in this procedure. You can then move it back to its original state and restart, without hunting down the old version.
Some users may also wish to keep things a bit cleaner and create a directory to store their old dashd files. That's fine too.
Step 6: Copy the new version of dashd and dash-cli to the desired directory
You can check that the new dashd and dash-cli are where you need them.
Step 7: Set read, write and execute permissions on dashd (if you wish)
You can first check on the current settings.
And modify them if you wish. I suggest following.
Step 8: Launch the new version of dashd
Step 9: Check the current version to make sure everything was done correctly
You should see the current version as "120058"
Step 10: Ensure that your IP is listed in the masternode list
You should see your IP address listed as "ENABLED" with a ":9999" at the end if everything is working properly. If you don't get that result, wait a few seconds and try again.
EDIT: As long as you upgrade quickly, the masternode should establish itself as active. If you wait a long period and still cannot get your IP address to come up as active, you may need to go back to your local console and restart your masternode. If your IP address is not listed right away after performing step 10, you should wait about 15 seconds and try running the "masternode list" command again. Your IP might not show up the first time you try, but may show up after a few seconds. If it still doesn't show up after you give it a few minutes, go back to your cold wallet's console and restart the masternode. From your cold wallet's console, enter "walletpassphrase <your passphrase> 60" followed by "masternode start-alias" and the alias of the masternode to start your masternode again. However, remote starting your masternode will cause it to fall to the back of the payment queue, so you only want to do this when absolutely needed.
Step 11: Get rid of all those files we no longer need
First, let's remove that entire set of files in the new dash-0.12.0 directory and all subdirectories, along with the packed .tar.gz file.
Everything should be gone from the file download. Next, scan through what's there and if there are some older dashd and dash-cli versions you've been holding on to and no longer want, let's remove those too. This is where naming the versions of your old files comes in handy. In this example, there are old copies from version 0.12.0.56.
Step 12: After 30-60 minutes, go to https://dashninja.pl/ to check to see that your version number is showing as updated
Step 13: Provide any feedback on this guide, especially if there are steps at which you struggled, and I'll try to make it more clear
https://dashpay.atlassian.net/wiki/display/DOC/Update+to+0.12.0.58+Guide+for+noobs
Note that dash-cli may not be necessary to replace, but I always replace it just in case something has changed.
Step 1: Once logged into your linux server, identify the location of "dashd" and "dash-cli" - these are the files we aim to replace
Most guides have users place dashd and dash-cli in the main directory while others place them inside a dash directory. No worries, it should be easy to find. Let's take a look at your files. Navigate to the main login directory and determine the location of these files.
Code:
cd ~
la
Code:
cd ~/.<directory name here>Step 2: Get the version number of your current dashd masternode
This will be useful if you plan to keep copies of your old dashd
Code:
./dash-cli getinfoStep 3: Now we need to get the new files
Code:
wget https://www.dash.org/binaries/dash-0.12.0.58-linux64.tar.gz
Code:
laStep 4: Now we need to unpack the contents
Code:
tar xfvz dash-0.12.0.58-linux64.tar.gzStep 5: Stop your old dashd and move the old binaries to a new name
This example assumes that you were previously running 12.0.57, and really you could name the old dashd and dash-cli whatever you want if you'd like to use a different naming convention than I've suggested below. It is a good idea to keep at least one old copy of an earlier version of dashd around just in case there is a "rollback" or major bug discovered or you get hung up on a later step in this procedure. You can then move it back to its original state and restart, without hunting down the old version.
Code:
./dash-cli stop
mv dashd dashd-120057
mv dash-cli dash-cli-120057Step 6: Copy the new version of dashd and dash-cli to the desired directory
Code:
cp dash-0.12.0/bin/dash-cli dash-cli
cp dash-0.12.0/bin/dashd dashd
Code:
laStep 7: Set read, write and execute permissions on dashd (if you wish)
You can first check on the current settings.
Code:
ls -la dashd
Code:
chmod 755 dashdStep 8: Launch the new version of dashd
Code:
./dashdStep 9: Check the current version to make sure everything was done correctly
Code:
./dashd-cli getinfoStep 10: Ensure that your IP is listed in the masternode list
Code:
./dash-cli masternode list full | grep <your.IP.address>EDIT: As long as you upgrade quickly, the masternode should establish itself as active. If you wait a long period and still cannot get your IP address to come up as active, you may need to go back to your local console and restart your masternode. If your IP address is not listed right away after performing step 10, you should wait about 15 seconds and try running the "masternode list" command again. Your IP might not show up the first time you try, but may show up after a few seconds. If it still doesn't show up after you give it a few minutes, go back to your cold wallet's console and restart the masternode. From your cold wallet's console, enter "walletpassphrase <your passphrase> 60" followed by "masternode start-alias" and the alias of the masternode to start your masternode again. However, remote starting your masternode will cause it to fall to the back of the payment queue, so you only want to do this when absolutely needed.
Step 11: Get rid of all those files we no longer need
First, let's remove that entire set of files in the new dash-0.12.0 directory and all subdirectories, along with the packed .tar.gz file.
Code:
rm -rf dash-0.12.0
rm dash-0.12.0.58-linux64.tar.gz
la
Code:
rm dashd-120056 (or whatever older versions you want to clean out)
rm dash-cli-120056Step 12: After 30-60 minutes, go to https://dashninja.pl/ to check to see that your version number is showing as updated
Step 13: Provide any feedback on this guide, especially if there are steps at which you struggled, and I'll try to make it more clear
https://dashpay.atlassian.net/wiki/display/DOC/Update+to+0.12.0.58+Guide+for+noobs
Last edited:
