Quick Start Qredit Node

You are here:
< Back

Version 1.0 24 Oct 2018 by Wazzy

if text is in BOLD it is to be copied or run exactly as given,
if text is in italic, its usually information related to previous script or run command
if text is bold and in italics, it is important info and must be understood before moving on

[October special with Digital Ocean] (100$ signup bonus) 20 x 5$ base server instances or 20 months of a single server free,
I have only seen it with credit card option and not with paypal option

Cost saving alternative :
Arubacloud.it 1 € per month for the basic random server instance, but expect below average customer support however specifications are almost identical to the digital ocean base. What i did was use the credit finished with digital ocean and then moved over to Aruba for 1 euro price.

To install and run Qredit Node on the Qredit Blockchain you will need:

ubuntu 16.04 server 64bit installed on a minimum 1gb Ram and 25gb hard drive server instance, cloud or local.
Ubuntu 18.04 will install but your node will fail to connect to the commander and you will have a log that looks like this:

new block recieved: ####################################

if you see this, then you probably installed the 18.04 ubuntu server. Reinitiate a new server with Ubuntu 16.04

So, lets set up a node and delegate to forge……

using putty or terminal:
(digital ocean will email password and you will be required to create new password on first access to the server and remember, by default you cannot see the cursor when entering passwords as well as the right click of the mouse is the paste function, so if you right click a copied text for pasting, you do not need to CTRL V or select paste, paste happens automatically on the right click

Putty: enter Ip Address and check port 22 OPEN and click save session, for later access.
Click Open and Yes to save new SSH key to local hosts file
then enter
root and password (yourinput)
Terminal always run
SSH (user)@(ip address of server)

once in root, run the following command:
sudo apt-get update && sudo apt-get upgrade
yes to any prompts asking permission.
after update complete run

After your OS has been updated and upgraded with latest releases of required packages, Run

sudo adduser (your username / delegate name)
— in creating a new user, new password required as well as info data. If you are creating this profile for someone else, its wise to complete the name etc, but if this is just for you, enter through the fields and just select y to save.
then run
sudo usermod -aG sudo (your username)
—— this is to give the new user profile admin rights and editing permissions to system files.

Normally this point will exit out of putty so you can log in on the new users name, but the switch user command is much quicker, so switch users to install Commander in user location.

su -l (your username) —switches you to (userprofile)

in user profile, run

git clone https://github.com/HodlerCompany/qredit-commander

—this will download the installation or setup file for the Qredit Commander which is what unpacks and installs and manages the Qredit block chain software

Then

bash qredit-commander/qredit-commander.sh

–first a system check is done and any missing required files or updates will then be downloaded and applied.
When system is updated and all required files updated, you must reboot your server so the new startup will have the changes applied.

Run
sudo reboot
—get error message is normal, close all session windows and wait 2 minutes for your server to reboot the os and apply any changes / updates.

Putty or Terminal back into
root@(serverIP)
then
su -l (yourusername) to switch to user that has the commander installation

then run

bash qredit-commander/qredit-commander.sh  and put in your user password if prompted. The Commander landing screen should open after entering user password. You will now install the node software,

Select 1 for install Qredit Node
yes to all selection points and paste 1st Passhphrase of registered delegate without space in front or after last word, makes sure you have 12 words in your phrase,
Yes to apply new configuration
—now your node is installed and is connected to the chosen delegate you will use for votes for as well as block reward payouts.
—Make sure to create a second passphrase in your wallet / client as the node you’re running now contains your first passphrase. If ever hacked, your pass phrase is exposed and your funds are at risk unless you have the second passphrase
After successful installation and delegate registration, you need to sync your node to the Qredit Block Chains current height, so
choose 4 to rebuild database
click yes to download latest snapshot, yes to restore current snapshot with latest snapshot
*—the snapshot is a up to date (within 15 minutes) snapshot of the entire block chain from the first block until the latest block. The higher the block height the longer the restoration takes to sync your node to the network, and every new installation will have the snapshot that was used when packing / writing the final code to the installation files. so your node will be seeing the blockchain as it was at the start. If you fail to sync then you will receive your block to forge when your delegated turn but the network will reject it as your node is forging already forged blocks. This may create a fork which is immediately rejected by the network. So sync first when troubleshooting or installing, this will usually solve or be The download of the snapshot is quick, and small file but restoring the latest snapshot to your new node may take a while. The older the block chain the longer it will take to restore your nodes copy of the block chain exactly and identically as seen by the whole network.

after snapshot restored, check your nodes block height and compare it to the network, http://explorer.qredit.cloud/will show you block height, Which network (mainnet or test net) and current supply

–synced nodes will be receiving updated block heights as they are forged by fellow delegates, every 8 seconds your node log should show a new entry received.

Choose L for node log and use
CTRL C to exit log screen at any point
—-the log is a live network block reporting tool and a synced node log will show you a new block received every 8 seconds as its forged by a delegate and the height number of the block

—The node log will always report a higher block number than what the explorer page will display, as your node is reporting in real time as soon as a block is forged.

!!!

With all the above steps successful the last step is to save the delegates wallet address so your node reports and pulls data from the right wallet.
Choose S for Node Status and save your Qredit Wallet Address for the delegate when prompted.
— this is instructing the commander which address is the delegate address, which was connected via passhprase in the initial set up of the node…..!!!!!Do not save the passhprase here, only the Qredit Wallet Address for the registered delegate !
The status should show
FORGING: TRUE / FALSE
Wallet Balance
Vote Approval %
Ranking and position

Press any key to exit and run

now

R – Restart Node

Select 0 to exit commander

exit out of user profile back to root user,
exit out of ssh session

Troubleshooting:
If your installation or updates take too long, putty and terminal cut your connection to the server after a certain amount of time, this may cause your installation to be interrupted and usually the process that was busy stays locked which will prevent your installation from running again or completing.

If you were kicked out of the SSH session in the middle of the node installation, you will likely get an error no NTP installed and you should install it manually first before proceeding, try
sudo apt-get install ntp
—if you get this error:
*E: Could not get lock /var/lib/dpkg/lock – open (11: Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?

you will need to kill the NTP process from the failed install attempt. Run
ps -A | grep apt — process ID displayed of stuck process then run
sudo kill (processnumber)
then

sudo apt-get install ntp

if this doesn’t install you may need to run

sudo dpkg –configure -a  and select yes for package default

Then run

Qredit Commander Home Screen Commands
1 Install Qredit Commander
2 Re-install Qredit Commander
3 Upgrade Commander
4 Rebuild Database
5 Set / change Secret Passphrase
6 Node Status
7 Other Options
0 Exit

Q  – Start Qredit Node

R  – Restart Node

T – Kill Qredit Node

S – Node Status

L – Log

0 – Exit commander

cheat sheet,
— — — — — — — — — — — — — — — — — — — — — — — — —
Restarting your qredit node: forever restart app.js
— — — — — — — — — — — — — — — — — — — — — — — — — —
— — — — — — — — — — — — — — — — — — — — — — — — — —
Real-time log of your qredit node: tail -f ./logs/qredit.log
— — — — — — — — — — — — — — — — — — — — — — — — — —
— — — — — — — — — — — — — — — — — — — — — — — — — —
Killing your qredit node process: forever stopall
— — — — — — — — — — — — — — — — — — — — — — — — — —
— — — — — — — — — — — — — — — — — — — — — — — — — —
Listing your forever processes (qredit node): forever list
— — — — — — — — — — — — — — — — — — — — — — — — — —
— — — — — — — — — — — — — — — — — — — — — — — — — —
Updating your qredit node : git pull
After updating, you need to restart the node: forever restart app.js
— — — — — — — — — — — — — — — — — — — — — — — — — —

Last Updated On January 08, 2019