Masternode Setup Guide

Transcription

1 Masternode Setup Guide This guide will help you to setup a Lizus masternode on an Ubuntu bit Server. Requirements LIZ ( LIZ for the initial transaction and 0.1 LIZ for covering the fee) - A Qt wallet (We ll use the Windows Wallet) - A server (Ubuntu that will be online 24/7) - (OPTIONAL) WinSCP ( (Please keep in mind that for security reasons you re gonna need a single IP for each masternode you re planning to run) Getting the Ubuntu Server ready Updating Once you ve logged in for the first time on your new Ubuntu Server you should always update your package lists from the repositories. apt-get update Installing needed libraries The LIZ-Daemon needs some basic libraries in order to run. Let s get them: apt-get install git automake build-essential libtool autotools-dev autoconf pkg-config libssl-dev libboost-all-dev software-properties-common add-apt-repository ppa:bitcoin/bitcoin apt-get update && apt-get install libdb4.8-dev libdb4.8++-dev libminiupnpc-dev

2 Compiling the Daemon Getting the newest version git clone OR updating an existing LIZ cd lizus-core && git pull Compiling the source cd src chmod 755 leveldb/* make -f makefile.unix Once your LIZ source is compiled without an error you can skip the following step Running the Daemon the first time Running the Daemon the first time will help us to create the basic folder structure and to check for errors. /root/liz/src/lizusd (For the ones who compiled on their own server) Editing the configs Once you ve run the Daemon for the first time, it will show you to setup a rpcuser and rpcpassword and close right after it - it has also created the folder structure where the blockchain and all config files are going to be. We want to edit those files now slightly but we ll come back later for the finishing touch. The easiest way is to use WinSCP to edit your conf-files. If you are somehow don t want to use WinSCP follow these steps:

3 apt-get install nano Nano is a great console-based text-editor. nano /root/.liz/lizus.conf Let s open the lizus.conf located in the.liz folder. This folder was created by the daemon on the first run! What goes inside the config? Your configuration files gets read by the LIZ-Daemon on startup. There are a lot of things you can tweak, add or remove. This is just a basic configuration for a simple masternode setup: ############################################### ## MY MASTERNODE_01 ############################################### rpcuser={choose A RANDOM USER} rpcpassword={choose A RANDOM PASSWORD} rpcallowip= listen=1 server=1 daemon=1 logtimestamps=1 maxconnections=256 masternode=1 externalip={your SERVER IP} masternodeprivkey={yourprivkey - WE WILL GET THAT LATER} addnode= addnode= addnode= addnode= Save the config and let s get over to the main-wallet.

4 Main wallet setup In order to get the masternodes to run, we need to send LIZ to an address we are just going to create. We use a system called Cold-Wallet. This system is meant for better security because actually your masternode won t have any access to your wallet. Masternode Priv-Key As you might ve saw we need a masternodeprivkey - this key indicates a private key that is used by your wallet and the masternode. In your Wallet-App go to: Tools -> Debugconsole. masternode genkey This will generate a private key - We need to add that key to the masternodeprivkey -field in the liz.conf on the Ubuntu server. Generate a wallet-address Each masternode needs it s own address. We are going to send LIZ to this address later. getaccountaddress MASTERNODE_01 You can change MASTERNODE_01 to whatever you want to name your masternode. Save the address you ve just generated for the next step. Sending LIZ to the address Let s send LIZ to that address. Yes - make sure this is only LIZ. No less, no more.) Wait for the transaction to have at least 15 confirmations before continuing. I won t get further into sending LIZ. Getting the transaction For our local masternode-config we need to get the transaction id and following number. Back into the main-wallets debugconsole enter: masternode outputs It will display a list of valid masternode transactions. If this is your first masternode there will be only one for sure. The list contains a longer number (transaction ID) and a following number. Save both of these somewhere for the next step.

5 Local configs We are almost there. Just a few lines to edit and we are able to start our masternode. lizus.conf Open your local liz.conf (Find it or use the Edit config file in the LIZ-QT client under Tools ). Make it look similiar to this: rpcuser={choose A RANDOM USER} rpcpassword={choose A RANDOM PASSWORD} rpcallowip= addnode= addnode= addnode= addnode= masternode.conf Open your local masternode.conf (You can find it or open it like you ve opened the lizus.conf via the Wallet-App) {YOURMASTERNODENAME} {YOURIP}:19700 {YOURMASTERNODEPRIVKEY} {TRANSACTIONID} {TRANSACTION_FOLLOW_ID} which should result in something like that: MN_ : abcdefgh dcba 1 Starting everything up After editing all the files locally we need to get back to our Ubuntu Server and enter the masternodeprivkey and for sure start the daemon. As I ve told you in the step where we ve created the privkey, we need to add that to the lizus.conf on our server. Get back to that step if you are not sure how to open the config. Starting the daemon on the Ubuntu server After adding the masternodeprivkey in we want to start the daemon.

6 /root/liz/lizusd OR /root/liz/src/lizusd (If you ve compiled on your own) The daemon should start minimzed. You ll only see a message like this one: LIZUS server starting Remote-Start the masternode Once you ve restarted your Wallet-App get back into the debugconsole and enter: masternode start-alias {YOURMASTERNODENAME} Enjoy your masternode ;)