Lemon Validator Set Up

set up ssh key you will need a ssh key to properly secure you vm which hosts the validator (and for the instructions to properly work the easiest way to generate a public and private ssh key is through a terminal if you are using a mac or linux machine, a terminal is built right in if you are using windows, you will need to install a terminal or jump through hoops using putty to generate a ssh private and public key pair windows wsl to get a terminal on windows, you need to install wsl please do a google search for setting up wsl or troubleshooting the installation the basics are as follows type cmd in the search bar, right click the cmd app that shows up in the search, select “run as administrator” at the command prompt, type the following wsl install if everything is ready on your machine, it will install and ask you to reboot if there are problems, it will ask you to turn on some windows services, or maybe turn on virtualization in your bios google is your friend generate an ssh key pair using terminal (mac) below document describes how to generate ssh key pairs using the linux terminal this is a common task for secure remote access and authentication open your terminal and use the ssh keygen command ssh keygen t rsa b 4096 c " your email\@example com mailto\ your email\@example com " where t rsa specifies the type of key (rsa) b 4096 sets the key length to 4096 bits for strong security c adds a comment (usually your email) to help identify the key you'll may be prompted to choose a location to save the key pair (otherwise it will create it in the folder you are currently in; if you change the name, pay attention to what you name it) enter file in which to save the key (/home/username/ ssh/id rsa) press enter to accept the default location, or specify a custom path next, you'll be asked to enter a passphrase (don’t use a passphrase) enter passphrase (empty for no passphrase) enter same passphrase again while optional, a passphrase adds an extra layer of security the system will generate your key pair and show a confirmation like your identification has been saved in /home/username/ ssh/id rsa your public key has been saved in /home/username/ ssh/id rsa pub view your public key with (this displays the key in text in the terminal; you can copy it to paste it into a text editor, or most importantly, into the ssh key upload field when creating your validator vm) cat / ssh/id rsa pub you'll now have two files id rsa your private key (keep this secure and never share it) id rsa pub your public key (this can be shared with services like github or servers) putty on windows to create and use ssh keys on windows, you need to download and install both putty, the utility used to connect to remote servers through ssh, and puttygen, a utility used to create ssh keys on the putty website, download the msi file in the package files section at the top of the page, under msi (‘windows installer’) next, install it on your local computer by double clicking it and using the installation wizard after the programs are installed, start the puttygen program through your start menu or by tapping the windows key and typing puttygen the key generation program looks similar to this you can customize the parameters at the bottom if you like, but the default values are appropriate in most situations when you’re ready, click the generate button on the right hand side you might be prompted to “generate some randomness by moving the mouse over the blank area” this randomness, known as entropy, is used to create keys in a secure fashion so that other people can’t reproduce them when the key is generated, you see the public key displayed in a text box copy this into your clipboard now if you plan to add it to your digitalocean account or to servers scroll carefully within the text area so you copy the entire key next, you are prompted to enter a passphrase for your ssh key this improves security by preventing someone who gains access to your private key from using it without also knowing the passphrase you need to provide your passphrase every time you use this key (unless you use ssh agent software that stores the decrypted key) when you’re done, click the save private key button and select a secure location to keep it you can name your key whatever you’d like, and the extension ppk is automatically added if you have not entered a passphrase, you need to confirm that you want to save the key without one we strongly recommend using a passphrase, but you can press enter to bypass this prompt optional convert to openssh format click "conversions" in the menu select "export openssh key" for compatibility with linux systems working with putty’s public key format you can click save public key as well, but take note the format puttygen uses when it saves the public key is incompatible with the openssh authorized keys files used for ssh key authentication on linux servers if you need to see the public key in the right format after the private key has been saved open puttygen next to load an existing private key file , click the load button navigate to the private key in your file system and select it click open set up your validator vm with in8 morpheus follow the directions below to set up a vm on the morpheus cloud console lemon installation connect to the vm via ssh with terminal open terminal and type (replace ‘ ssh/id rsa’ with the name of your private key file and the location if it is not in the current folder) ssh i ssh/id rsa ubuntu@\<your public ip here> accept the cert by typing “yes” with putty you need to add your private key file to putty in the proper section and make sure to save the profile so you can reload it in the future when you connect again again, google is your friend after that, connect in the main window using ubuntu@\<your public ip here> it should look something like this lemon install continued run the following commands (you can highlight the whole thing and copy it; you paste into the terminal by right clicking) wget https //assets allthingslemon io/validators/setup node bash https //assets allthingslemon io/validators/setup node bash p / chmod 744 /setup node bash this downloads an optimized script written by kory we will be modifying it to work with the in8 morpheus vm’s next we need to find out where our volume is located so we can mount it to the right place lsblk you are looking for the disk that is 1000g, the take note of the name you will need this in the next step nano setup node bash this will open the nano editor program to edit the setup node bash file you need to use your arrow keys to navigate in the editor you can’t use go places using the mouse you need to use the arrow key to move the cursor and change the 3 “nvme1n1” entries to the name of 1000gb drive you need to delete the last two lines of the file we are doing this so the script will complete (and we can make sure there are no error) before starting the validator into archive mode and syncing the blockchain) after making the changes, press ctrl x it will prompt you to “save modified buffer?” press 'y' it will then ask you the file name to write it will be already populated just press the “enter” key now, enter the following command to start the script /setup node bash this will install and compile everything you need for the validator it may complain about an ext files system on the volume that you are going to overwrite, just hit 'y' it should complete with no error if you have any errors, make note and bring it to the validator group for community help from here, we will start the validator into archive mode by running the following command /start node bash it will run for around two hours (as of this writing) to sync the chain if you want to monitor the progress (and make sure it is working properly), enter the following command tail f /nohup validator you can get back to the command prompt by pressing ctrl c (this will not stop the validator) configure cron job you need to configure a cron job so your validator starts up in the event of a reboot of the vm run crontab and select option 1, nano crontab e use the arrow keys to move the cursor to the end of the file (below all the hash lines) paste the following @reboot sleep 30 && /home/ubuntu/start node bash press ctrl x; y to save buffer; and < enter > to save it to the file enter the following command sudo systemctl enable cron service create wallet & prepare validator open nano nano paste the following code into nano \#!/bin/bash \############################################################### \#this script is to create the wallet and deploy the validator# \############################################################### \#check if validator is already initialized if \[ f /extra/validator ] then echo "validator file is already there so stoping deployment" exit 0 fi \# create validator wallet echo "creating your validator wallet" echo "please enter a strong password recommended it be 20 or more characters " read walletpwd echo "$walletpwd" >> /home/ubuntu/privpwd /go opera/build/opera account new datadir=/extra/lemon/data password=/home/ubuntu/privpwd > /extra/validator 2> /extra/validator errors echo "wallet password $walletpwd" rm rf /home/ubuntu/privpwd \# create validator key echo "creating validator key" echo "please enter a strong password recommended it be 20 or more characters " read valkeypwd echo "$valkeypwd" >> /extra/lemon/password /go opera/build/opera validator new datadir=/extra/lemon/data password=/extra/lemon/password >> /extra/validator 2>> /extra/validator errors echo "validator key password $valkeypwd" chmod 400 /extra/lemon/password \# prep preload js file wallet address=`cat /extra/validator | grep 'public address'` wallet key=`cat /extra/validator | grep 'public key'` \#storing password, public key and public address in preload js password=`cat /extra/lemon/password` publickey=`cat /extra/validator | grep "public key" | cut d " " f 2 | tr d " "` publicaddress=`cat /extra/validator | grep "public address" | cut d " " f 2 | tr d " "` preload file=preload js preload=/extra/${preload file} asset base url=" https //assets allthingslemon io/validators https //assets allthingslemon io/validators " \# downloading file and appending the contents to make sure no duplication \# echo "deleting existing file to make sure copy is updated" rm rf /extra/preload js \# echo "downloading preload file for ${network}" wget o "${preload}" "${asset base url}/${preload file}" pass=`echo $password |sed e 's/^/"/;s/$/"/'` echo e "\npassword = $pass" >> /extra/preload js pubkey=`echo $publickey |sed e 's/^/"/;s/$/"/'` echo "publickey = $pubkey" >> /extra/preload js pubaddress=`echo $publicaddress |sed e 's/^/"/;s/$/"/'` echo "wallet = $pubaddress" >> /extra/preload js echo "tokenstake = 250 00" >> /extra/preload js if \[ f /extra/validator ] then echo "validator deployment is completed" echo echo "generating details for you" echo "wallet address" echo e "$wallet address" echo echo "wallet private key copy this and save to a text editor with json extention" for privatekey in /extra/lemon/data/keystore/ut ; do cat "$privatekey" done echo echo "private key password write this down, do not lose" echo "$walletpwd" echo echo e "$wallet key" echo echo "public key password this has been saved to /extra/lemon/password so you don't need to enter it every time your validator starts " echo "$valkeypwd" echo echo echo "your wallet is now ready to fund make sure to fund 250 1 lemx before moving to the next steps " fi press ctrl x press y save files as wallet setup sh at the command prompt run the following chmod 744 wallet setup sh /wallet setup sh you will be prompted for a password for your wallet creation do yourself a favor and use a password generator with 20 characters and paste it in you only get one time to enter this, so make sure you have what you want before hitting enter the password will be displayed to you at the end of this process for you to copy if you didn’t have it copied already you will then be prompted for a password for the validator key do yourself a favor and use a password generator with 20 characters and paste it in you only get one time to enter this, so make sure you have what you want before hitting enter the password will be displayed to you at the end of this process for you to copy if you didn’t have it copied already the process will finish and present you with all your addresses, passwords, keys for you to copy and paste places (this includes the private key for you to copy and paste into a text editor) copy important stuff with everything listed, take the time to highlight the information, copy and paste it to your local computer in particular, copy the private key, paste it into a text editor, then save that file with the json extension fund wallet take your new found wallet information and go fund your wallet with 250 1 lemx you cannot proceed further without funding your wallet make sure to stake your tokens before moving to the next step complete validator setup this process only works if you used the above scripts to create your wallet after you have funded your wallet with 250 1 lemx and staked move to this next step open nano nano paste the following code into nano \#!/bin/bash \# this script is for completing validator setup after staking \# check to see if the wallet setup sh script was used to create the wallet if \[ f /extra/validator ] then echo "proceeding" public key=`cat /extra/validator | grep "^public key" | sed e 's/public key //g' | tr d " "` validator id=`/home/ubuntu/go opera/build/opera attach preload /extra/preload js datadir=/extra/lemon/data exec '!!abi && !!sfcc ? sfcc getvalidatorid(wallet) console log("problem")'` sed i 's/startup mode=1/startup mode=3/g' /home/ubuntu/start node bash sed i "s/^validator id=/validator id=$next/g" /home/ubuntu/start node bash sed i "s/^public key=/public key=$public key/g" /home/ubuntu/start node bash sed i "s/cache=4096/cache=12288/g" /home/ubuntu/start node bash echo e "finalizing the final registration process" echo "running node in validator mode" bash /home/ubuntu/start node bash echo "process is complete" elseif echo "this script is only compatible with the use of the wallet setup sh script for wallet creation and validator preparation " exit 0 fi press ctrl x press y save files as valmode setup sh at the command prompt run the following chmod 744 valmode setup sh /valmode setup sh this script will check to make sure the setup files created in with the wallet setup script are present before proceeding it will then proceed to setup the validator get a validator id, stake the validator, properly config the start node bash file (including adjusting the memory cache to the proper recommendation), and restart the validator in validator mode note i got the opportunity to test this with a user for whatever reason, it is not retrieving the validator id you will need to manually add the validator id when you register your wallet (prior to staking), the dashboard will show you your validator id make note of that use nano to edit the start node bash file and add the validator id to the file where it says “validator id=” after you add that, save the file, the run /start node bash everything is done if you want to retrieve your validator id, you can type nano start node bash it will be the value listed “validator id=” enjoy!