Welcome to the Dash Forum!

Please sign up to discuss the most innovative cryptocurrency!

TAO'S MASTERNODE SETUP GUIDE FOR DUMMIES (UPDATED FOR 12.1)

Discussion in 'Masternode Guides' started by TaoOfSatoshi, Oct 15, 2014.

  1. TaoOfSatoshi

    TaoOfSatoshi Grizzled Member
    Linguistic Dash Nation Founder

    Joined:
    Jul 15, 2014
    Messages:
    2,371
    Likes Received:
    2,423
    Trophy Points:
    1,183
    ***GUIDE UPDATED FOR 12.1 AND SENTINEL, FEBRUARY 2017***

    For 12.1 UPDATE guide, please click here: https://dashtalk.org/posts/25672/

    For those I linked here who are from outside of the community: The Masternode network is a group of de-centralized nodes which aid in the process of PrivateSend Mixing. They are eligible to receive payments, as a reward! Anyone can set up a Masternode, the only pre-requisite is 1,000DASH. Understand, you are not committed to anything, you can quit and sell your DASHs at any time.

    WELCOME TO TAO'S MASTERNODE SETUP GUIDE FOR DUMMIES!

    Hi, and welcome to you, who are interested in setting up a DASH Masternode! I have found Masternode ownership to be a very rewarding experience, teaching me about computers and different operating systems, as well as making me extra money for DASH that would just be sitting in my wallet anyway!

    BEFORE YOU BEGIN, YOU WILL NEED:

    - 1,000 DASH
    - The latest DASH wallet, which can always be found here: https://www.dash.org/wallets/
    - Some USB thumb drives
    - Two Windows programs (PuTTY: http://www.putty.org/, and WinSCP: http://winscp.net/eng/download.php#download2. Installation Package)
    - A VULTR account, which can be found here: https://www.vultr.com/
    - An ability to follow instructions to the letter

    I'm TAO OF SATOSHI, and I will be your guide through this understandably intimidating set-up. You will be just fine, please take it slow, and be sure to thoroughly follow the instructions.

    Be aware, you are setting up a Masternode on a remote server, and keeping your DASH on a local Windows PC. Your DASH are never in danger from the remote server, and I will show you how to run this Masternode with your wallet offline/cold so your DASH will not be in danger on your Windows PC either. Please practice safe computing and backup your wallet regularly, as I will show you how to do.

    Happy Masternoding!

    Any questions or comments feel free to post below. Remember, I am trying to make this guide as easy as possible, and would welcome feedback to that end.

    All images in this thread are credited to WeirdGod, I used them from his guide for more advanced users.

    If you value this guide and have found it easy to use, please show me some DASH love at:


    XgUJ1vpJN49YTEnBJxZ6dfhTrQmyF4Ecuw

    (Tao's New Masternode Fund :D)


    LET'S GET STARTED!

    First, you will need to prepare the Windows PC and the DASH Wallet (dash-qt.exe) to support the Masternode setup.

    Please bear in mind the following safety tips:

    - Always do a backup of your WALLET.DAT if you have DASH on your computer.
    - Think twice before deleting or overwriting anything, as there is no way back...Post here for help.
    - Never copy WALLET.DAT when your wallet is running! Please use the BACKUP WALLET command from within your wallet instead.

    This guide is going to assume that you have a clean PC with no DASH wallet installed. If you have installed a DASH wallet already, you are ahead of the game. Congratulations, you eager beaver! You get to skip the next line, only:

    Download the latest Windows version of "dash-qt.exe" (the DASH wallet) as found on this page: https://www.dash.org/wallets/

    ----- Create new directory c:\dashcore.

    Move the "dash-qt.exe" file to this new directory.

    Fire up your new DASH wallet. Feel that engine purr! You may get a security pop up from your virus scanner, please override.


    Now please go for a coffee, run to the grocery store, or do whatever you have to do while you wait for your wallet to fully sync with the network.

    It should look like this, "out of sync" until it is fully caught up with the network.

    [​IMG]

    Oh, you're back! I guess the wallet has finished syncing with the network! You are now ready for the next step:

    On your Desktop, create a new notepad file.

    Back in your wallet, click on TOOLS, then DEBUG CONSOLE.

    [​IMG]

    You will find the command line at the bottom of the console.

    Enter the following command: "masternode genkey" and press ENTER.

    You will see a long string of numbers and letters.

    Please copy/paste this string to the new notepad file on your Desktop. This is the key you will need to verify your Masternode later in the process.

    Enter the following command: "getaccountaddress 0" and press ENTER.

    This will generate your new Masternode's receiving address!

    Please copy/paste this string to the notepad file, as well.

    Please note: This address will be the one that you will send your 1,000DASH to, and the one where all future payments will go.

    Congratulations, you are getting closer. Still lots to go through, so bear with me!

    Once you have copy/pasted these items into your notepad file, you are finished with the Console. You may now close it, and return to the Overview screen.

    A visual of the last step:

    [​IMG]

    Important safety procedure time!

    Begin securing your wallet by clicking on SETTINGS, ENCRYPT WALLET.

    Enter a password, repeat it, and click OK.

    Do not forget your password! Keep it somewhere safe, as you do not want to lose your DASHs!

    IMPORTANT:
    I recommend that you type your password into your notepad file, and then cut/paste into the password field so you are sure of what your password will be. This is a big investment, and it pays to be sure!

    You will see your DASH wallet may become unresponsive for several seconds, this is normal. Please do not hit any keys until your wallet has finished encrypting. Once your wallet has finished and closed, you are ready for the next security step:

    Re-run your wallet (dash-qt.exe) and immediately go to FILE, BACKUP WALLET.

    [​IMG]

    Select the location where you want to store a copy of your WALLET.DAT, and backup your wallet.

    Please note: I recommend backing up your wallet to several USBs to keep in different locations
    .

    I can't stress this enough: BACKUP regularly! You never know with hard drives these days!

    Financing your Masternode (depositing 1,000DASH to your "0" address):

    Please check your wallet Overview screen. If you see that the big button under PrivateSend says "Stop PrivateSend Mixing", please click on it to disable PrivateSend. If you see that the button says "Start PrivateSend Mixing", you are good to go to the next step:

    From wherever you currently hold your 1,000DASH (exchange, another DASH wallet, even a different address in the same wallet), please send your DASHs to your new "0" Masternode receiving address in your wallet. Make sure the "PrivateSend" checkbox is unchecked.
    IMPORTANT: You must send EXACTLY 1,000DASH to this address, no more, no less, to be eligible to run a Masternode! (VIN 1,000)

    Once you have initiated the transaction, you must wait for 15 confirmations so your address is eligible to be associated with your new Masternode. This usually takes about 40 minutes on average.

    This time, you're lucky however, you don't have to wait! You can let the DASH blockchain do it's thing while you move on to the next post:
     
    #1 TaoOfSatoshi, Oct 15, 2014
    Last edited: Feb 10, 2017
    • Like Like x 14
  2. TaoOfSatoshi

    TaoOfSatoshi Grizzled Member
    Linguistic Dash Nation Founder

    Joined:
    Jul 15, 2014
    Messages:
    2,371
    Likes Received:
    2,423
    Trophy Points:
    1,183
    You are now ready to configure your Linux VPS! I will guide you thoroughly through this process, so stop sweating! You will be fine.

    Remember the VULTR account I told you to create above? We will need it now. If you have not created this account, tsk, tsk, pay attention! See the post above under "What you will need" for directions.

    See this testimonial by WeirdGod:

    "For Linux server, I am using VULTR. Why VULTR instead of Amazon EC2? In short: simpler, cheaper, better. In detail: Vultr is awesome new self-provisioning, budget, virtual private server (VPS) provider. Built upon infrastructure of gameservers.com, they offer 12+ locations around the globe, many server/OS configurations all with fast SSD drives...

    VPS can be obtained from $5/month (charged hourly at $0.007/hour) - making it 3x cheaper than Amazon EC2 where t1.micro starts at $0.02/hour. Additionally, currently they have 2 for 1 deposit bonus! So, deposit $10, and get $20 of credits - enough to run your VPS for 4 months!

    I used many VPS providers (including DigitalOcean and Amazon), and I prefer VULTR, because it has clean interface and great features (snapshots, own OS installation from ISO image, windows instances...). I am impressed with them, and so was everyone who tried them."


    I am also using this VPS provider for all of my nodes.

    Please login to your newly created VULTR account.

    - Click DEPLOY NEW INSTANCE
    - Select Server Type: PERFORMANCE
    - Select datacenter location: Your choice, the primary locations offer DDOS protection.
    - Select OS: The latest Ubuntu 16.04 or higher (64 bit)
    - Select Server Size: 1 CPU with 1024MB of RAM is the minimum spec for a Masternode.

    [​IMG]

    It will take 30 seconds for your new server to come online. Click MY SERVERS, and if you see your new VPS's IP and a MANAGE button, you are good to enter your VPS's main page.

    In your VPS's main page, make a note of the initial password.

    You will see a VIEW CONSOLE button. Please click this to interface with your VPS. Please note, for freshly installed servers, you will see the installation progress in the CONSOLE window until your OS is finished installing. When you see a command prompt, you are ready for the next step:

    [​IMG]

    [​IMG]


    I'm not going to lie, you're doing great so far! Let's continue.

    Login to your freshly-made VPS using the information provided in your VPS's main page (login as "root", and use the supplied initial password).

    Once logged in, the first thing you will need to do is change ROOT's ;) password. ROOT ;) is the administrative default user that comes with your VPS.

    To change ROOT's ;) password, enter the following command (you must always hit ENTER after all commands):

    passwd root

    You will need to create a new password, and repeat the new password.

    Next you will need to create a friendlier, more personal user. Sorry, ROOT! :sad: Please enter the following commands:

    adduser YOUR NEW USERNAME

    passwd WHATEVER PASSWORD YOU WANT

    You will see prompts for information, this is not necessary, just keep hitting enter and then Y to get to the command prompt again.

    So now you have 2 users, ROOT ;) and new user, hopefully with different passwords....

    Now you may bid farewell to ROOT for now, :sad:, by closing the CONSOLE. Please stay logged into your VULTR account, though.

    You will now need to fire up the PuTTY program I told you to download and install under "What you will need" above.

    With PuTTY, login to your VPS using it's IP which can be found in your VULTR account under MY SERVERS, and your new user login information you created in the previous step.

    Once you see a command prompt, you're going to visit good old ROOT again, ;), by entering the following command:

    su -

    Enter ROOT's ;) password which you created before.

    Security is important on this side too, so you must now secure your VPS.
    (Updated: Cheers thelonecrouton!)

    Enter the following commands:

    apt-get update

    You will see a lot of things happening, just wait for them to stop.

    apt-get install ufw

    Enter the following commands EXACTLY (in this order) to set up your firewall:
    Please note: Make sure you enter the code in this order! If you do not, the program will not work! If need be you can disable your firewall by entering (as root;)): ufw disable.

    ufw allow ssh/tcp

    ufw limit ssh/tcp ---this command limits SSH connections to 6 every 30 seconds for greater security---

    ufw allow 9999/tcp

    ufw logging on

    ufw enable



    Check your firewall's status by entering the following command:


    ufw status

    You will see a message saying that your ufw status is active and will activate upon reboot as well.

    Congratulations, you now have a firewall!

    Please note, this is a minimum security procedure, and will be fine for the short term. Long term, you may want to further harden the server. It is recommended you read the following excellent "El Presidente" Chaeplin’s thread, and also some guides below, which also describe security settings:

    https://www.darkcointalk.org/threads/how-to-set-up-ec2-t1-micro-ubuntu-for-masternode-part-2-3.241/
    http://konstruktoid.net/2014/04/29/hardening-the-ubuntu-14-04-server-even-further/
    http://forums.linuxvoice.com/viewtopic.php?f=3&t=147
    https://www.digitalocean.com/community/tutorials/initial-server-setup-with-ubuntu-14-04
    http://www.tecmint.com/linux-server-hardening-security-tips/

    By now, you are really rolling with this Linux OS, aren't you! And you were worried? This is a piece of cake! Moving on....

    Enter the command "exit" to ditch poor ROOT again, :sad:, and return to your newly created user.

    Leave PuTTY running, but continue to the next step:

    Enter the dashd......

    You are now ready to download and install "dashd" and "dash-cli" on your VPS. "dashd" is the beating heart of your masternode. It holds all the nuts and bolts that make your masternode tick.

    "Geez, Tao, you like to talk a lot, don't you? Let's get on with it...."

    Visit DASH.ORG with this link https://www.dash.org/wallets/, and download the latest Linux .tgz file.

    Extract the file using whatever extractor program you use to wherever you want on your PC.

    Locate the beating heart "dashd" and "dash-cli" by clicking on the extracted Linux file, and navigating to BIN, 64, dashd/dash-cli.

    Copy and paste these two files to your desktop.

    You will now need the second downloaded program from the "What you will need" section, WinSCP!

    Please note, WinSCP is what us dummies use as a liaison between your Windows PC and your Linux VPS. You will need this program every time you would like to transfer the latest dashd from DASH.ORG to your VPS from your Windows PC.

    Fire up WinSCP. Login to your VPS using your IP and user information, the same as PuTTY.

    You will see on the left is your Windows PC, and on the right your Linux VPS.

    Above your VPS on the right, you will see a folder icon with a star on the top right. Please click this icon to create a new folder.

    Please name this folder .dashcore.

    Double click your new .dashcore folder to open it.

    On the left, navigate to your two files, and drag and drop them to your new folder on the VPS! It's that easy to transfer it!

    You are now finished with WinSCP, and may now exit.

    Going back to PuTTY....

    You now need to make the files executable as well, like your firewall.

    Enter the following commands:

    cd .dashcore
    chmod 777 ./dashd
    chmod 777 ./dash-cli


    Your "dashd" will be ready to serve it's purpose as the beating heart of your Masternode!

    You are not going to start it just yet however...

    Again, leave PuTTY running.

    Back on your PC....

    You now need to create a customized .dashcore/dash.conf file.

    Open a new notepad file. We will go back to the first one later.

    Copy/paste the following information into your new notepad file.

    #----
    rpcuser=XXXXXXXXXXXXX
    rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXX
    rpcallowip=127.0.0.1
    #----
    listen=1
    server=1
    daemon=1
    maxconnections=24
    #--------------------
    masternode=1
    masternodeprivkey=XXXXXXXXXXXXXXXXXXXXXXX
    externalip=XXX.XXX.XXX.XXX


    Customize this file by replacing the four fields in XXXXXXXXXXXXX.

    Please note: rpcuser and rpcpassword can be anything, but it cannot have any special characters such as $,#,!, only letters and/or numbers. The masternode privkey is the one that you generated in your wallet and copied to your notepad file earlier, and externalip is your VPS's IP.

    Once you have properly customized this file, please copy it.

    Continue on to the next post! :D
     
    #2 TaoOfSatoshi, Oct 16, 2014
    Last edited: Feb 12, 2017
    • Like Like x 7
    • Informative Informative x 1
    • Useful Useful x 1
  3. TaoOfSatoshi

    TaoOfSatoshi Grizzled Member
    Linguistic Dash Nation Founder

    Joined:
    Jul 15, 2014
    Messages:
    2,371
    Likes Received:
    2,423
    Trophy Points:
    1,183
    OK, we are almost done. Sorry for the interruption, I have a character limit to respect...Moving on!

    Where were we? Oh yes, I remember.

    Back to PuTTY....

    You are now going to need a program called "Joe's Own Editor". This is a Linux editor which will help you create and edit files in your VPS.

    To install "Joe's Own Editor", enter the following commands:

    su - (to visit ROOT ;) again)

    apt-get install joe

    Return to your personalized user by entering:

    exit

    Excellent! Joe :cool: will be your hired gun to help you conquer this Masternode beast!

    You will need Joe :cool: to help you place your customized .dashcore/dash.conf file into it's place on your VPS. Enter the following command:

    joe .dashcore/dash.conf

    You will see a blank window with .dashcore/dash.conf at the top.

    Please paste your customized, copied file into Joe's :cool: window.

    Save and exit your .dash/dash.conf file by using the following keys:

    CONTROL - K - X

    For added security, it is recommended to make this file "Read Only" so no one can change it:

    chmod 444 .dashcore/dash.conf

    You are now ready to start the beating heart....

    Run your dashd daemon:

    cd .dashcore
    ./dashd


    You will see the message "Dash Server Starting". Let it sync while you move on to the next step.

    Back on your Windows PC, there is one more thing you need to do....

    Remember the dash.conf file you and Joe :cool: created on your VPS? You now need to create a masternode.conf file on your Windows PC, to link with it.

    We'll now use the first notepad file you created at the beginning.

    The masternode.conf file needs to have the following information:

    LABEL: A one word name you make up to call your node (ex. MN1)
    MN IP : PORT: Your masternode VPS's IP, and the port is always 9999.
    MASTERNODEPRIVKEY: This is the result of your "masternode genkey" from earlier.
    TRANSACTION HASH: The collateral tx. hash from the 1000DASH deposit.
    INDEX: The Index is always 0 or 1.

    The MN IP and MASTERNODEPRIVKEY should already be in your notepad file, and the LABEL you make up yourself, so you just need to find out the TRANSACTION HASH and INDEX. To get your transaction hash and index, open your wallet and go to TOOLS=>DEBUG CONSOLE.

    On the command line, enter "masternode outputs".

    You will get a string that looks like this:
    {
    "06e38868bb8f9958e34d5155437d009b72dff33fc28874c87fd42e51c0f74fdb" : "0",
    }

    The long string is your transaction hash, and the last number is the index. You now have all the information you need.

    The masternode.conf must look like this (no spaces between MN IP and PORT):

    LABEL MN IP : PORT MASTERNODEPRIVKEY TRANSACTIONHASH INDEX

    Example:
    MN1 52.14.2.67:9999 XrxSr3fXpX3dZcU7CoiFuFWqeHYw83r28btCFfIHqf6zkMp1PZ4 06e38868bb8f9958e34d5155437d009b72dff33fc28874c87fd42e51c0f74fdb 0


    Great! You now need to save this file in the same folder as your wallet.dat. If you didn't change it, this folder should be here: C:\users\YOURUSERNAME\AppData\Roaming\Dashcore. You may need to enable the "view hidden files" feature in your Windows Explorer to see this folder.

    ---- Please note, make sure that you save under file type "All files" as Windows will default to a text file. It must be saved as a .conf file in order to work. Please verify it is saved as a .conf file! ----

    Please shut down and re-start your Dash Core QT wallet. This is so the program recognizes the masternode.conf and is ready for masternode activation.

    You are so close....let's wrap it up on your VPS!


    Run Joe again as root to give your personalized user sudo powers:

    su - (to visit root ;) for the last time)

    joe /etc/sudoers

    In Joe's window, find the line that says the following:

    root ALL=(ALL:ALL) ALL and make another line underneath it like this:
    YOURUSERNAME ALL=(ALL:ALL) ALL

    Control-K-X to save and exit to root.

    exit (to go back to your personalized user who is now a sudoer and may perform the following task):

    You must install Sentinel. Sentinel is a watchdog for your node which communicates to the network that your node is working properly.

    step 1) install prerequisites

    sudo apt-get update
    sudo apt-get install -y git python-virtualenv


    step 2) If you are not already there, navigate to your .dashcore folder

    cd .dashcore

    step 2) clone sentinel, switch to the sentinel directory

    git clone https://github.com/dashpay/sentinel.git
    cd sentinel


    step 3) create virtual python environment

    virtualenv venv

    (if this command fails try installing this package:)

    sudo apt-get install -y virtualenv

    step 4) install sentinel dependencies

    venv/bin/pip install -r requirements.txt

    step 5) test sentinel is alive and talking to the still sync'ing wallet

    venv/bin/python bin/sentinel.py

    You should see: "dashd not synced with network! Awaiting full sync before running Sentinel."
    This is exactly what we want to see at this stage

    step 6) wait until the reindex has complete and the wallet has sync'd

    cd .. (you should now be back in .dashcore)
    ./dash-cli mnsync status

    This is what you're waiting to see:

    AssetId 999, all trues, one false, and a FINISHED. Keep issuing ./dash-cli mnsync status until it looks like this:

    {
    "AssetID": 999,
    "AssetName": "MASTERNODE_SYNC_FINISHED",
    "Attempt": 0,
    "IsBlockchainSynced": true,
    "IsMasternodeListSynced": true,
    "IsWinnersListSynced": true,
    "IsSynced": true,
    "IsFailed": false
    }


    At this point, your remote masternode is synchronized and chatting with the network
    but is not accepted as a masternode because it hasn't been introduced to the network
    by your collateral.

    Step 7) You may now start your masternode! Go back to your local wallet, open the debug console, and run these commands (LABEL is the name you used for your MN in the masternode.conf):

    walletpassphrase <YOURPASSPHRASE> 120
    masternode start-alias <LABEL>


    to (hopefully :)) start your masternode.

    step 8) test sentinel has nothing to say

    You're needed back in Sentinel directory! :D

    cd sentinel

    At this point, running

    venv/bin/python bin/sentinel.py

    should return nothing but silence. This is how you know it's working, and your masternode is working.

    step 9) create a crontab entry to wake sentinel every five minutes

    crontab -e

    Choose Joe as your editor. Add this line to the end of the file.

    * * * * * cd /home/YOURUSERNAME/.dashcore/sentinel && ./venv/bin/python bin/sentinel.py 2>&1 >> sentinel-cron.log

    Make sure you:
    1) Change USERNAME to your username.
    2) Hit enter to create another line at the end after this line, or the file will not work.


    Press Control-K-X to save and exit.

    step 10) check for start, try, try, again

    cd ..

    You should be back in .dashcore.

    ./dash-cli masternode debug

    Did it work? You should see the message "successfully started masternode".

    "Yes, Tao, you're a genius! Thanks for that exhaustive process, it was worth it!" :D

    If not, you may have to re-send your masternode start.


    to do it a second time, repeat step 7.

    How about now?

    "No, I will have to go retrace my steps, thanks for trying bud!" :(

    Hopefully it was the former and not the latter. Congratulations!

    Once you have confirmed your node is running, you are now free to shut down PuTTY, and your DASH wallet on your PC. That's it, you're done!:D :cool:

    Your Masternode will keep on
    PrivateSend Mixing and receiving payments, smooth as silk....

    CONGRATULATIONS AGAIN, AND HAPPY MASTERNODING!





    --------Now that you are a Masternode Jedi, I can teach you some tricks:


    Dash Info and Masternode Monitoring websites:

    There is a Dash Ninja site to monitor your Masternode for updates or issues:

    https://www.dashninja.pl run by @elbereth.

    This fellow Dasher runs this website on his own time. If you find the site useful, show him some DASH love as well. His address will be posted on the site.

    Dash TV, by @pille, great for monitoring your masternode's value and expected monthly payment:

    https://dash-news.de/dashtv/#curr=USD&addr=

    Simply follow the (=) with your masternode or regular addresses (each separated by a comma) and bookmark for later access.

    Updates:

    With the way this Dev team innovates and churns out updates, you may also find this helpful in the future:

    TAO'S MASTERNODE UPDATE GUIDE FOR DUMMIES:

    https://dashtalk.org/threads/taos-masternode-setup-guide-for-dummies.2680/#post-25672

    Withdrawing profits:

    At some point in the future, you may want to send funds from your Masternode, but don't want to risk messing it up and having to start again. For this trick, please click here:

    https://dashtalk.org/posts/26705/



    "THANKS FOR THIS TAO, HOW CAN I EVER REPAY YOU?"


    I don't seek fame, but I could use some DASH love here for Tao's New Masternode Fund, if you appreciated my work! Hmm? Nudge, nudge..

    :cool:XgUJ1vpJN49YTEnBJxZ6dfhTrQmyF4Ecuw:cool:

    Also, you may consider participating in the DASH TWITTER PR INITIATIVE. See my signature below for details.


    Thank you for using my guide, and good luck in the future, fellow Dasher!

    Tao Of Satoshi

     
    #3 TaoOfSatoshi, Oct 16, 2014
    Last edited: May 11, 2017
    • Like Like x 16
  4. HinnomTX

    HinnomTX Active Member

    Joined:
    Jul 22, 2014
    Messages:
    166
    Likes Received:
    196
    Trophy Points:
    103
    Vultr is a great choice! You can copy instances live to deploy new masternodes with minimal effort. If you're good with iptables, you can deploy 3 masternodes per instance by getting 3 IPs.
     
    • Like Like x 3
  5. Ignition75

    Ignition75 Active Member

    Joined:
    May 25, 2014
    Messages:
    332
    Likes Received:
    206
    Trophy Points:
    113
    Excellent guide mate, well done!
     
    • Like Like x 1
  6. oblox

    oblox Well-known Member

    Joined:
    Aug 6, 2014
    Messages:
    1,034
    Likes Received:
    539
    Trophy Points:
    183
    You don't need to install joe, just use nano.
     
    • Like Like x 1
    • Agree Agree x 1
  7. aaxx1503

    aaxx1503 Active Member

    Joined:
    Feb 28, 2014
    Messages:
    113
    Likes Received:
    106
    Trophy Points:
    93
    Very clean guide, well done Tao.
     
    • Like Like x 1
  8. TaoOfSatoshi

    TaoOfSatoshi Grizzled Member
    Linguistic Dash Nation Founder

    Joined:
    Jul 15, 2014
    Messages:
    2,371
    Likes Received:
    2,423
    Trophy Points:
    1,183
    This is for dummies, from me to them. I found joe extremely easy to use.
     
  9. TaoOfSatoshi

    TaoOfSatoshi Grizzled Member
    Linguistic Dash Nation Founder

    Joined:
    Jul 15, 2014
    Messages:
    2,371
    Likes Received:
    2,423
    Trophy Points:
    1,183
    Thank you for your kind words.
     
  10. aaxx1503

    aaxx1503 Active Member

    Joined:
    Feb 28, 2014
    Messages:
    113
    Likes Received:
    106
    Trophy Points:
    93
    Give me your DRK address and I'll thank you with some kind DRK (Freshly Darksent, finally went through!)
     
    • Like Like x 1
  11. TaoOfSatoshi

    TaoOfSatoshi Grizzled Member
    Linguistic Dash Nation Founder

    Joined:
    Jul 15, 2014
    Messages:
    2,371
    Likes Received:
    2,423
    Trophy Points:
    1,183
    Thanks, man! Appreciated.

    This was needed, in my opinion, to cut down the intimidation factor for the vast majority of people.
     
  12. aaxx1503

    aaxx1503 Active Member

    Joined:
    Feb 28, 2014
    Messages:
    113
    Likes Received:
    106
    Trophy Points:
    93
    No problem, just Darksent you some DRK!
     
    • Like Like x 1
  13. TaoOfSatoshi

    TaoOfSatoshi Grizzled Member
    Linguistic Dash Nation Founder

    Joined:
    Jul 15, 2014
    Messages:
    2,371
    Likes Received:
    2,423
    Trophy Points:
    1,183
    That's awesome! I'll never know where it came from...:D
     
    • Like Like x 1
  14. yidakee

    yidakee Well-known Member
    Dash Core Team Foundation Member

    Joined:
    Apr 16, 2014
    Messages:
    1,812
    Likes Received:
    1,168
    Trophy Points:
    283
    Top job Tao !! Nice work!
     
    • Like Like x 1
  15. oblox

    oblox Well-known Member

    Joined:
    Aug 6, 2014
    Messages:
    1,034
    Likes Received:
    539
    Trophy Points:
    183
    Nano is just as easy and it's one less thing to install.
     
    • Like Like x 1
  16. Dr.Crypto

    Dr.Crypto Member

    Joined:
    Jul 9, 2014
    Messages:
    46
    Likes Received:
    32
    Trophy Points:
    58
    Thanks for the great tutorial!
    As I'm in the process of setting up my first masternode, I was wondering: how do you specify where the masternode payments go? Do you directly go to the same address that contains the initial 1000 DR?
     
    • Like Like x 1
  17. TaoOfSatoshi

    TaoOfSatoshi Grizzled Member
    Linguistic Dash Nation Founder

    Joined:
    Jul 15, 2014
    Messages:
    2,371
    Likes Received:
    2,423
    Trophy Points:
    1,183
    Thanks! I'm glad you like it!

    The payments will go to the Masternode receiving address. I don't think it is currently possible to change this. Good luck with your setup!
     
    • Like Like x 1
  18. TaoOfSatoshi

    TaoOfSatoshi Grizzled Member
    Linguistic Dash Nation Founder

    Joined:
    Jul 15, 2014
    Messages:
    2,371
    Likes Received:
    2,423
    Trophy Points:
    1,183
    Thank you! Appreciated.
     
  19. TaoOfSatoshi

    TaoOfSatoshi Grizzled Member
    Linguistic Dash Nation Founder

    Joined:
    Jul 15, 2014
    Messages:
    2,371
    Likes Received:
    2,423
    Trophy Points:
    1,183
    WELCOME TO TAO'S 12.1 MASTERNODE UPDATE GUIDE FOR DUMMIES!

    Q. "What gives, Tao? I stopped receiving payments, and elbereth's site doesn't show my node anymore!"

    A. "You'll have to update your node to 12.1, then! Welcome to life as a DASH Masternoder!"

    You will need to be prepared to regularly update your Masternode, as we have a genius Dev team that has a penchant for pushing out innovation daily it seems. This is not a bad thing!

    Fear not, I will guide you through this relatively simple process as well. Before beginning, make sure your VPS has at least the following specs:

    1Ghz CPU 1GB RAM 20 GB Disk 400GB bandwidth per month.

    What you will need:

    - The latest Windows Dash wallet (dash-qt.exe)
    - The latest Linux .tgz file package (32 or 64, depending on your VPS specs)

    Both can be found here: https://www.dash.org/wallets/
    - Your two Windows programs, PuTTY and WinSCP
    - An ability to follow instructions


    This process is really no sweat. Follow the directions closely.

    On your Windows PC (If your wallet is running, please stop it and wait 60 seconds before proceeding):


    Navigate to your dash wallet folder. If your folder has a custom name, no change is required. If you have a Dash folder, please rename the folder to Dashcore.

    In the folder, delete debug.log, and all .dat folders (EXCEPT WALLET.DAT!!!)

    Move your freshly downloaded dash-qt.exe file to your wallet folder directory.

    You will get an action prompt, please choose "Replace file in the destination"

    Run the 12.1 wallet. Answer yes to reindexing the blocks, as 12.1 uses a different way of indexing, and the whole blockchain will need to be re-synced.

    Let the wallet re-sync, and move on to your remote VPS!

    On your computer:

    Extract the contents of your Linux .tgz file. Place the programs dashd and dash-cli on your desktop.
    If you left your old dashd and dash-cli file there from your original installation, replace this file as well, when prompted.

    In your VPS, using PuTTY:

    Using your VPS's IP address and login information, login to your VPS under your username.

    Once logged in, you will see the command prompt.

    Enter the following commands:

    cd .dash
    ./dash-cli stop

    Wait 60 seconds for your daemon to shut down. Run ps aux to see if it's still running. Continue when you no longer see dashd in the listing.

    Logout and exit PuTTY.

    Now, we need to replace the current .dash folder with the new improved .dashcore version.

    Time for our liaison, WinSCP:

    Fire up WinSCP.

    Login to your remote VPS. On the left, you will see your local computer, and on the right you will see your remote VPS.

    On the right side, navigate to your /home/USERNAME folder.

    Right click and delete your .dash folder, and your .cache folder.

    In the menu above your remote VPS listing, you will see a folder with a star on the top right. Click this icon to create a new directory in your remote VPS.

    Name the new folder .dashcore.

    Once created and named, please double click on it to open.

    On the left (your Windows PC), navigate to your dashd and dash-cli on your desktop, and drag/drop them to your .dashcore folder in your Linux VPS on the right.
    I'm such a dummy, I love that move!

    Exit and close WinSCP.

    Back to PuTTY....

    Login again using your username.

    Change directory to .dashcore.

    cd .dashcore

    Make your new dashd and dash-cli files executable and active by entering the following commands:

    chmod 777 ./dashd
    chmod 777 ./dash-cli

    If you have Joe's Own Editor installed, great! If not, run apt-get install joe, and then enter the following:

    joe /home/USERNAME/.dashcore/dash.conf (Note: change USERNAME to your personal username)

    Copy the following and paste into the new file Joe's window:

    #----
    rpcuser=XXXXXXXXXXXXX
    rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXX
    rpcallowip=127.0.0.1
    #----
    listen=1
    server=1
    daemon=1
    maxconnections=24
    #--------------------
    masternode=1
    masternodeprivkey=XXXXXXXXXXXXXXXXXXXXXXX
    externalip=XXX.XXX.XXX.XXX


    In the window, replace all XXXes with your personalized information. rpcuser and rpcpassword can be anything (password longer than username), masternode privkey, and your VPS IP address.

    Save and exit the edited file by pressing Control-K-X.

    Start dashd.

    ./dashd

    Let the blockchain sync on your remote VPS while you move on to installing Sentinel. (Guide for this based on @moocowmoo's version)

    Install sentinel agent on masternode

    step 1) install prerequisites

    sudo apt-get update
    sudo apt-get install -y git python-virtualenv


    step 2) If you are not already there, navigate to your .dashcore folder

    cd .dashcore

    step 2) clone sentinel, cd to sentinel directory

    git clone https://github.com/dashpay/sentinel.git
    cd sentinel


    step 3) create virtual python environment

    virtualenv venv

    (if this command fails try installing this package:)

    sudo apt-get install -y virtualenv

    step 4) install sentinel dependencies

    venv/bin/pip install -r requirements.txt

    step 5) test sentinel is alive and talking to the still sync'ing wallet

    venv/bin/python bin/sentinel.py

    You should see: "dashd not synced with network! Awaiting full sync before running Sentinel."
    This is exactly what we want to see at this stage

    step 6) wait until the reindex has complete and the wallet has sync'd

    cd .. (you should now be back in .dashcore)
    ./dash-cli mnsync status

    This is what you're waiting to see:

    AssetId 999, all trues, one false, and a FINISHED. Keep issuing ./dash-cli mnsync status until it looks like this:

    {
    "AssetID": 999,
    "AssetName": "MASTERNODE_SYNC_FINISHED",
    "Attempt": 0,
    "IsBlockchainSynced": true,
    "IsMasternodeListSynced": true,
    "IsWinnersListSynced": true,
    "IsSynced": true,
    "IsFailed": false
    }


    step 7) start your masternode

    At this point, your remote masternode is synchronized and chatting with the network
    but is not accepted as a masternode because it hasn't been introduced to the network
    by your collateral.

    Go back to your local wallet, open the debug console, and run these commands:

    walletpassphrase <YOURPASSPHRASE> 120
    masternode start-alias <MNALIAS>


    to start your masternode.



    step 8) test sentinel has nothing to say

    You're needed back in Sentinel directory! :D

    cd sentinel

    At this point, running

    venv/bin/python bin/sentinel.py

    should return nothing but silence. This is how you know it's working.

    step 9) create a crontab entry to wake sentinel every five minutes

    crontab -e


    Choose Joe as your editor. Add this line to the end of the file.

    * * * * * cd /home/YOURUSERNAME/.dashcore/sentinel && ./venv/bin/python bin/sentinel.py 2>&1 >> sentinel-cron.log

    Make sure you:
    1) Change USERNAME to your username.
    2) Hit enter to create another line at the end after this line, or the file will not work.


    Press Control-K-X to save and exit.

    step 10) check for start, try, try, again

    cd ..

    You should be back in .dashcore.

    ./dash-cli masternode debug

    Look for a success message. If you see one, you are done!

    Because the network is in transition, you may have to re-send your masternode start.

    to do it a second time, repeat step 7.

    step 11) partytime!

    It's time to celebrate! You've done a great job! Treat yourself to something!
    Running a masternode, you can afford it! :)


    You have finished updating, and are all set.... until the next time!

    I'll still be here to help you, until you no longer need it!

    "Thanks again, Tao!"

    Hope you're enjoying your Masternode experience, and have received lots of payments! It's great, isn't it?

    If this guide was useful to you, please consider showing me some DASH love at this address:

    :DXgUJ1vpJN49YTEnBJxZ6dfhTrQmyF4Ecuw:D


    Until we meet again,

    Tao Of Satoshi

    To return to the Masternode guide, click here:
    https://dashtalk.org/threads/taos-masternode-setup-guide-for-dummies.2680/
     
    #19 TaoOfSatoshi, Oct 17, 2014
    Last edited: Feb 27, 2017
    • Winner Winner x 1
  20. oblox

    oblox Well-known Member

    Joined:
    Aug 6, 2014
    Messages:
    1,034
    Likes Received:
    539
    Trophy Points:
    183
    For updating the remote daemons, use the update script:

    nano update.sh

    Code:
    #!/bin/sh
    echo "########### This script will update the Master Node"
    sleep 5
    VERSION=64
    URL=$1
    FILE=${URL##*/}
    DIR=${FILE%.tar.gz}
    IP=$(hostname -I)
    wget $URL
    tar xzvf $FILE
    echo "########### Stopping the Master Node"
    ./darkcoind stop
    sleep 7
    rm darkcoind
    cp $DIR/bin/$VERSION/darkcoind .
    chmod 755 darkcoind
    rm $FILE
    rm -rf $DIR
    rm .darkcoin/peers.dat
    echo "########### Restarting the updated Master Node"
    sleep 30
    ./darkcoind
    sleep 15
    ./darkcoind getinfo
    sleep 20
    echo "########### Master Node status - Active: 1, Inactive: 0"
    ./darkcoind masternode list | grep $IP
    
    chmod 755 update.sh

    Then to update:

    ./update.sh https://raw.githubusercontent.com/darkcoinproject/darkcoin-binaries/master/rc/darkcoin-0.10.15.13-linux.tar.gz

    ^^ or whatever is the latest release in *.tar.gz format.
     
    • Like Like x 4
  21. TaoOfSatoshi

    TaoOfSatoshi Grizzled Member
    Linguistic Dash Nation Founder

    Joined:
    Jul 15, 2014
    Messages:
    2,371
    Likes Received:
    2,423
    Trophy Points:
    1,183
    You are correct, sir!

    Correct, but not quite for dummies....You really love this nano thing, don't you?

    Thanks for your contribution! Respect.
     
  22. calnaughtonjnr

    calnaughtonjnr Well-known Member
    Foundation Member

    Joined:
    May 25, 2014
    Messages:
    218
    Likes Received:
    158
    Trophy Points:
    203
    Tao, I finally got round to attempting this. I have got to the final command, masternode start. When I run this, I get a message saying...

    you must set masternode=1 in the configuration

    I have a darkcoin.conf in the correct location and it does have, on line 9, masternode=1. Can you help..?

    EDIT: Tao, I restarted my machine and the masternode started successfully. Thanks so much for taking the time to do this. Will send you some coins over to show appreciation...
     
    #22 calnaughtonjnr, Oct 21, 2014
    Last edited by a moderator: Oct 21, 2014
    • Like Like x 1
  23. TaoOfSatoshi

    TaoOfSatoshi Grizzled Member
    Linguistic Dash Nation Founder

    Joined:
    Jul 15, 2014
    Messages:
    2,371
    Likes Received:
    2,423
    Trophy Points:
    1,183
    calnaughtonjnr Great, I'm glad my guide helped you to build the Darkness! As far as gratuities, they are always appreciated.... Welcome to the MN club!
     
  24. TaoOfSatoshi

    TaoOfSatoshi Grizzled Member
    Linguistic Dash Nation Founder

    Joined:
    Jul 15, 2014
    Messages:
    2,371
    Likes Received:
    2,423
    Trophy Points:
    1,183
    WITHDRAWING FUNDS FROM MASTERNODE WALLETS:

    Q. "Hey Tao, I want to show you some DASH love! How can I send DASH from my node without messing it up?"

    A. "You are going to need a feature called "Coin Control". This will allow you to specify where your withdrawals come from, so you will not touch your 1,000VIN."

    Here's how you set it up:

    Start your wallet.

    Go to Settings, Options, and click on the 4th tab named "Display"

    Check the box that says "Display Coin Control features (experts only)
    That's right, you're now an expert! :D

    Click OK, and you are ready to use the feature next time you send.

    Sending without touching the 1,000VIN:

    Go to your Send tab.

    Click on the button that says "Inputs"

    You will see a box with your wallet balance next to it. Click on the little arrow next to the box.

    You will see all the deposits to your wallet, and your 1,000VIN should be at the top.

    To send your full non-masternode affecting balance, click on the boxes next to ALL OTHER deposits.

    Or, you could just click on as many as you need for a particular transaction.

    Please note: Be careful not to select the 1,000VIN!

    Please click OK.

    You will be back to the main Send window.

    The total number of selected deposits will show, as well as the total DRK amount.

    Send anything up to and including the MAX amount that you saw in the previous step, making sure to uncheck the "Darksend" checkbox.

    That's it! Your Masternode lives another day!:D

    Thanks for using my guide,

    Tao Of Satoshi

    To return to the Masternode guide, click here:
    https://darkcointalk.org/threads/taos-masternode-setup-guide-for-dummies.2680/
     
    #24 TaoOfSatoshi, Oct 24, 2014
    Last edited by a moderator: Apr 18, 2015
  25. lostmybrain

    lostmybrain New Member

    Joined:
    Sep 23, 2014
    Messages:
    17
    Likes Received:
    14
    Trophy Points:
    3
    Thank you for the guide! I seem to be having one issue though. I don't see any output when I enter "grep HotCold .darkcoin/debug.log" in my terminal in putty, and my node shuts down if I close my local wallet. What could be the issue?
     
    • Like Like x 1
  26. TaoOfSatoshi

    TaoOfSatoshi Grizzled Member
    Linguistic Dash Nation Founder

    Joined:
    Jul 15, 2014
    Messages:
    2,371
    Likes Received:
    2,423
    Trophy Points:
    1,183
    Thanks for helping to build the Darkness! I'm sorry you're having issues. When you enter the HotCold command, what happens?
     
  27. coingun

    coingun Administrator
    Dash Core Team Dash Support Group Moderator

    Joined:
    Jul 8, 2014
    Messages:
    485
    Likes Received:
    396
    Trophy Points:
    133
    Example's please! You can't tease us with this goodness and then hold out the tables!
     
  28. lostmybrain

    lostmybrain New Member

    Joined:
    Sep 23, 2014
    Messages:
    17
    Likes Received:
    14
    Trophy Points:
    3
    Absolutely nothing! A new command line appears.
     
  29. HinnomTX

    HinnomTX Active Member

    Joined:
    Jul 22, 2014
    Messages:
    166
    Likes Received:
    196
    Trophy Points:
    103
    Alright, I'll post my script. Give me a day to retrieve it. I'm on a tablet at the moment. :)
     
    • Like Like x 1
  30. TaoOfSatoshi

    TaoOfSatoshi Grizzled Member
    Linguistic Dash Nation Founder

    Joined:
    Jul 15, 2014
    Messages:
    2,371
    Likes Received:
    2,423
    Trophy Points:
    1,183
    Please stop your darkcoind on your remote server, wait a minute or two, restart it and then start on your local wallet. Then, run the line ./darkcoind masternode list / grep YOUR IP. Does your node show up there? If so, the HotCold command should work. Post your reply.
     

Share This Page