The downloads can be found here: https://www.energi.world/downloads/
Launch the Energi client. You’ll then want to navigate to Settings > Options, and click the Wallet tab. Check the box for “Show Masternodes Tab”
You will need 10,000 NRG to set up a masternode. To do so, follow these steps:
Sign up for a free account at aws.amazon.com
You will need to start a t2.micro Ubuntu 16.04 instance in Amazon Web Services. This will be your virtual machine that hosts the masternode. To do this:
In the EC2 Management Console, on the left, under the “Network & Security” dropdown, click Security Groups. We will be creating 2 separate security groups. For each security group, click “Create Security Group” and add two rules on the inbound tab.
One security group will open port 9797, and the other will open port 22.
Your security groups should look something like this:
Once you have your security group filled out correctly, click Create. Do this for both security groups.
On the Instances page, select your instance, then click the “Actions” dropdown menu and select Networking > Change Security Groups.
Make sure the Energi and SSH security groups you created are selected, and uncheck the default selection. Then click “Assign Security Groups”
You may then go back to the Security Groups page and delete the default security group that you unchecked.
This software will let you ssh and sftp to your virtual machine from your local computer.
Launch the software!
The remote host should be your IPv4 Public IP (found in the description menu of your instance, in the instances tab in the Amazon EC2 Management Console).
The username is “ubuntu”, port is 22. Under the “Advanced SSH settings” tab, click “Use Private Key” and load the .pem file you saved in step 3 when you first set up the virtual machine. Then, click OK.
In your SSH session, enter the following commands:
sudo apt update
sudo apt upgrade
You should end up with a file named
energi.tar.gzto your home directory on the virtual machine.
tar -xvzf energi.tar.gz
.bashrcfile with MobaTextEditor.
At the very end of the file add this line:
save and exit.
This will update the environment variables you just specified in the .bashrc file. To log out type
exit, and then hit the
R key to restart your session.
To test if you’ve done everything correctly so far, enter this command:
You should get an error message about shared libraries. We will install these next.
enter these commands:
sudo apt-get install software-properties-common
sudo add-apt-repository ppa:bitcoin/bitcoin
sudo apt-get update
sudo apt install libboost-dev libboost-system-dev libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev libevent-pthreads-2.0-5 libminiupnpc10 libzmq5 libdb4.8 libdb4.8++
This time, you should get a help menu, and no errors about missing dependencies. There will be a “Too Few Arguments” error after the help menu displays, this is normal.
Navigate back to your home directory. To do this, type the following command:
in your home directory (/home/ubuntu), enter this command:
Navigate to the
.energicore directory in your SFTP session. In the
.energicore directory, right click, and select “New empty file”. Name it
energi.conf. Then, open the file with MobaTextEditor:
Enter these lines in your new
rpcuser=[invent a energi rpc user name]
rpcpassword=[put a password here]
externalip=[your ec2 instance public ip]
masternodeprivkey=[your masternode private key]
rpcpassword fields can be anything you want. Make sure there are no brackets. Your
externalip is the same public IP of your instance that you used to SSH and SFTP to. Once again, no brackets.
masternodeprivkey field, open up the debug console in your Energi wallet. Type in:
Put the resulting key in the
masternodeprivkey field (without brackets!) in the energi.conf file. You will also want to save and backup this key somewhere secure.
In the debug console of your Energi wallet, type in:
Save and backup this address somewhere.
Then, send exactly 10,000 NRG to this address.
Once again, in the debug console of your Energi wallet, type in:
You will need to add the resulting information to your
masternode.conf file in the next step
In your local wallet, edit
Alias is any name you want, be creative!
IP:Port is your AWS instance public IP, and the port is 9797.
masternodeprivkey is your master node’s private key (obviously), the same key you used in the
.energicore/energi.conf file, which you also should have saved from step 22.
collateral_output_index, enter the information you got from the
masternode outputs command in the previous step.
It should look similar to the example!
As you can see I have two masternodes listed. The masternode we are setting up for this tutorial is labeled
In your SSH session, from your home folder, enter the command:
You can check the status by running this command in SSH:
energi-cli mnsync status
When it’s syncing it will look something like this:
When it’s finished, it will look something like this:
In the debug console on your local Energi wallet, run this command:
You should see the same results.
Once you have 15+ confirmations on your collateral transaction, you’re ready to start your masternode.
Go to your local Energi wallet, and on the Masternodes tab, right click your masternode and select “Start Alias”
Feel the excitement.
Sentinel lets the network know that your masternode is still online and functioning correctly
Run the following commands:
git clone https://github.com/
sudo apt install -y virtualenv
sudo apt install -y python-virtualenv
venv/bin/pip install -r requirements.txt
A masternode is required to be online for a minimum amount of time per day to be considered a masternode. This crontab will let the Energi network know about the status of your masternode every minute
in your SSH session, type:
select a text editor, and on the last line of the file, paste this:
* * * * * cd /home/ubuntu/.energicore/sentinel && ./venv/bin/python bin/sentinel.py 2>&1 >> sentinel-cron.log
ctrl + X to save the file