How to setup & connect to your server instance
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Before setting up Raspberry Pi, check requirements here.
Connect the UPS to the power supply and let it charge.
Plug in the modem, the swith and the Raspberry into the UPS and access the Modem. Later we need to set up a fixed IP address and port forwarding (TCP 6000/9000/9500) for the Rasperry.
3.1. Install Heatsinker on Raspberry
3.2. Install Fan
3.3. Connect Mini HDMI -> HDMI cable (if you like, otherwise you can use SSH)
3.4. Connect the keyboard (if you like, otherwise you can use SSH)
3.5. Connect Ethernet
3.6. Install Ubuntu Server 20.04 LTS on MircoSD and on SSD. Click here for instructions
3.7. Start the UPS Power for the Raspberry
4.1. Access via Powershell, Terminal or directly via Keyboard and Monitor
4.2. Login: ubuntu / Password: ubuntu
For security reasons Linux requires to change the default ubuntu password.
4.3. Update & Upgrade
During update we can set up a static IP on the Modem and set up Port forwarding.
4.4. Restart
Code is adapted from an Instruction, check here if you need further information’s.
5.1. Download Eeprom
5.2. Restart
5.3. Connect the hard disk and check
5.4. Read out the SSD ID via and write it down
5.5. Mount the hard disk
5.6. Check again with point 5.3 if mount has worked
5.7. Automatically boot from SSD using this script
5.8. Create Quirks driver
In point 5.4. the SSD ID was read out via sudo lsusb xxxx:xxxx
Now connect the hard disk to a computer and add in /boot/firmware/cmdline.txt
“usb-storage.quirks=xxxx:xxxx:u”
in the first place, without the quotation marks and save. For example for the Samung T7, usb-storage.quirks=04e8:4001:u
5.9. Remove the MicroSD and boot from SSD
Now it should start from the SSD, let it around 20 Minutes so settle down everything, special if you have a bigger SSD.
In case it searches still for MicroSD, write with the Pi Imager «Misc utility images -> Bootloader -> USB Boot to the MicroSD, put it in and start the Rasperry, wait around 15 seconds, remove power and MicroSD and try again.
By starting from the SSD, the password must be changed again. Upon logging in for the first time if the Pi is connected to the internet Ubuntu will immediately/soon start a lengthy update process via snapd and apt.
Make sure you give the system enough time (20 Minutes at least) to finish this process before doing going forward.
Code is adapted from an Instruction, check here if you need further information’s).
7.1. Update by command
7.2. Restart by command
7.3. Change the keyboard to your Language (if wished)
7.4. Restart by command
7.5. Set the time zone
7.6. Restart by command
7.7. Speed testing of SSD via
8.1. Minimize GPU, deactivate Bluetooth, deactivate Wifi and overclocking
Add the following in the config file under [all]
Save via ctrl + x and confirm.
9.1. Change host name
Code is adapted from an Instruction, check here if you need further information’s).
9.2. Create user
Code is adapted from an Instruction, check here if you need further information’s).
Enter your new password and confirm again.
9.3. Give sudo permission
9.4. Check and even extend authorization
9.5. Add the entry for the new user in Visudo
Save via ctrl + x and confirm.
9.6. Terminate old processes and block users
9.7. Change to new User
Code is adapted from an Instruction, check here if you need further information’s).
10.1. Install & activate the firewall
10.2. Open the corresponding TCP ports for Harmony & local SSH from another PC
10.3. Check Firewall
Congratulation you set up your Raspberry Pi and it is ready for setting up as Node!
Since HMY CLI is not natively supported ARM systems yet, install it on a x86_64 system to setup the BLS Keys. After that, copy them to the same .hmy/blskeys
folder on Raspberry Pi.
Continue node setup from Rclone onwards.
To launch your AWS instance, follow the steps below.
1. If you don’t already have an AWS account, register one at https://aws.amazon.com.
2. Once you have set up and logged into your AWS account, click on the top left bar “Services -> Compute -> EC2".
3. Click on the blue button “Launch Instance".
4. Select “Amazon Linux 2 AMI (HVM), SSD Volume Type”.
5. Choose instance type “m5a.xlarge” or “m5.xlarge“.
6. Click “Next: Configure Instance Details” at the bottom right corner of the page.
7. Don't change anything. Click “Next: Add Storage” at the bottom right corner of the page.
8. Change the “Size (GiB)” accordingly to the minimum storage requirements.
9. Click “Next: Add Tags".
10. Click "Add Tag." Then, in the “Key” input box put “Name” in “Value” put “Pangaea-key”.
11. Click “Next: Configure Security Group”.
12. On the default SSH with port 22, change the “Source” option to “Anywhere”.
13. Click "Add Rule". Under "Type" select "Custom TCP Rule", under "Port Range" put "6000" and under "Source" select "Anywhere".
14. Click "Add Rule" again. This time, under "Type" select "Custom TCP Rule", under "Port Range" put "9000" and under "Source" select "Anywhere".
15. Click “Review and Launch” and then click "Launch". (Note: Ignore warnings such as “your security group is open to the world” or “your instance configuration is not eligible for free tier”)
16. In the pop-up window you will need to create a new key pair. Select “Create a new key pair” and then enter a name that you like, for example “Pangaea-key”.
17. Click “Download Key Pair” and save the key file somewhere you'll remember.
18. Click “Launch Instances”.
19. Click “View Instances” at the bottom right. Your new instance should be initializing. Wait a few moments for it to get started.
21. Congratulations your instance is up and running! Now it's time to connect to your instance.
1. Open a Terminal window on your computer.
For Mac: If you can’t find Terminal, use spotlight to search for it. Or go to your "Applications' folder, and it should be inside of “Utilities”.
For Windows: Download PuTTY to allow your computer to SSH into the AWS instance. For instructions on connecting to an EC2 instance using Putty follow these instructions from Amazon.
2. Once Terminal is open, use the cd
command to change your directory to where the key pair file (Pangaea-key.pem) that you generated is. Hint it may be in your “Downloads” folder.
3. Enter the command chmod 400 Pangaea-key.pem
. This command makes your key not publicly viewable.
Note: On Mac, your pem file may have been changed to a .txt file so the correct command on Mac would be: chmod 400 Pangaea-key.pem.txt
4. Go back to your AWS window where you are viewing your instances. Select your new "Pangaea-key" instance and click “Connect” on the top bar.
5. In the pop-up window, under the “Example:” header, copy the sample command to connect to your ec2 instance. The command will look something like:
Now connect to your instance by running the sample command you copied from the “Connect” page in your terminal window.
It may ask you whether or not you want to continue connecting. Type in “yes” and hit enter.
Congratulations! You should be logged into your new AWS instance!
Run the following command to make sure your instance is properly updated:
When prompted whether or not you want to download packages, enter "y" for yes.
It is forbidden now to run multiple nodes using the same set of BLS keys. As we are moving towards full decentralization, external validators will become the shard leader and start to propose blocks. If one validator runs multiple nodes using the same set of valid keys, they may all become valid leaders when the key is rotated to this validator, in this case, the blockchain is experiencing a high risk of hard-fork as different valid leaders may propose different blocks. So, do not run redundant validator nodes anymore on the Harmony blockchain. This is also strictly forbidden on all PoS blockchains such as Ethereum 2, Cosmos.
Specs | Shard 0 | Shard 1 |
---|---|---|
Cloud provider CPU's are usually shared unless you specifically chose a dedicated CPU or opt for a dedicated bare metal server
Here is a list of Cloud Providers (August, 2020):
Check Cloud Guides for instructions.
Same requirement as validator unless specified below:
Same requirement as validator unless specified below:
Same as above for the type of node you wish to run
A Raspberry Pi 4 with a good Fan and Heat sinker elements will be required Check Raspberry Pi Guide for instructions.
To launch your Digital Ocean instance, follow the steps below.
For new users, you can get $100 dollars free credits to run Digital Ocean services for 2 months using the link bellow
Click to register a new Digital Ocean account or login if you have an existing one.
Once you have set up and logged into your Digital Ocean account, click on the top left bar “Projects -> New Project". Enter the desired project name and click on "Create Project" as shown by the image below:
On the top right corner click on "Create"->"Droplets".
You can select the datacenter region of your choice here. We chose "Frankurt" in our example. We recommend using the "SSH Keys" as your authentication method (more secure) instead of the "One-time password" method. A button with the name "New SSH key" will appear on screen, just click on it.
When you generated your public SSH key, give it a name and click on button "Add SSH key" as shown by the image below. In case you don't have a public SSH key yet, just follow the instructions to create it.
Choose a custom hostname if you want and then click on "Create Droplet".
Wait a few seconds till your droplet is created and then click on "Networking" on the left bar.
Click on "Firewall" and then on "Create Firewall".
In the Inbound Rules section, click on "New rule" and select "Custom". Leave the protocol as TCP and fill the port range field with 6000. Repeat the same procedure for port 9000. You will be left with 2 inbound rules as shown by the image below.
In the Outbound Rules section leave it as it is. Type the name of the droplet you want to apply your firewall rules (the droplet name is the same as your hostname you chose previously).Click now on "Create Firewall".
Before anything, it is recommended to update your system:
You will be asked to confirm if you would like to download and install these packages. Just press Y to confirm.
To launch your Google Cloud instance, follow the steps below.
Google Cloud has a free tier for new users. You get $300 to spend on Google Cloud Platform products during your first 12 months
Go to and click on “Get Started for Free”. Login using an existing account or create a new one.
After you login and validate your credit card, you will be shown a page pretty much like this one. Click on “Compute Engine” and then in “VM Instances”.
Click on the Create button to make a new instance
We recommend to name it something like "pangaea” (the instance name cannot be changed). Select the Machine type as “Custom” and set up 4 vCPU’s and 4GB of Memory.
Keep everything default after you have configured the cores and memory.
Click Create. Please wait a few minutes for your instance
Once the instance is created. We will open 4 ingoing ports. To do this click on "nic0" as shown below. In the next page click on “Firewall rules” and after that on “CREATE FIREWALL RULE”.
TCP 6000
TCP 9000
Go back to the VM instances page and click on SSH. This will open a new window and connect via SSH to your instance:
Before anything, it is recommended to update your system:
You will be asked to confirm if you would like to download and install these packages. Just press Y to confirm.
To launch your Vultr instance, follow the steps below.
First, go to the . If you don’t already have an Vultr account, register one by clicking on "Sign up". Otherwise, log into your Vultr Account by clicking on "Sign in".
Once logged in, you'll want to add a new instance. Depending on whether your account is new or not, you may or may not have a Products page.
Otherwise, your Products page will be already link you to the Deploy page.
For Harmony, two instance types would fit: Cloud Compute and High Frequency.
Choose now your desired server type. We recommend the latest LTS version of Ubuntu (18.04 as of date of now).
You can now set the name of your server, e.g. PangaeaNode Then you should click "Deploy Now".
At this point you should be back on the Products page and your server should be installing. However, the setup isn't completely done, as you need to still create a firewall.
As we want to allow other nodes to connect to yours, we have to open the correct ports.
Enter a name for the firewall group, e.g. FoundationNode.
TCP 22 (SSH)
TCP 6000
TCP 9000
Make sure to check that 3 Group Rules have been set.
Click Linked Instances.
Make sure your new server is selected.
Click the + button.
Click Add Linked Instance.
Your instance should now be added to the firewall group and the number of linked instances should increment by 1.
You can now go back to the Products page and your server is now successfully set up!
Follow the instructions below accordingly to the operating system you are connecting from:
Before anything, it is recommended to update your system:
You will be asked to confirm if you would like to download and install these packages. Just press Y to confirm.
Specs | Shard 0 | Shard 1 |
---|---|---|
Shard 0 | Shard 1 | |
---|---|---|
Choose now your desired Linux image. We recommend the latest LTS version of Ubuntu (18.04 as of date of now). Use the left and right arrows to navigate between the different plans available. Choose the "Standard" plan and then select a virtual machine with at least 4 CPUs, 4GB of RAM and 80GB SSD accordingly to the .
To create your SSH key click for instructions.
To connect via SSH to your Digital Ocean instance, please follow the instructions .
For the Boot Disk, we recommend the latest LTS version of Ubuntu (18.04 as of date of now). Change the boot disk size to the .
If you already have an instance, click the "+" button to deploy a new server. You can also use this to go to the deploy page.
Harmony recommends one of the two following accordingly to the :
Once you are on the , click Add Firewall Group.
CPU
8 dedicated core
4 dedicated core
RAM
8 GB
4 GB
Storage
1 TB (using snapDB) SSD Minimum, NVMe recommended
100GB SSD Minimum, NVMe recommended
Network
50Mb/s bandwidth, 5~6 TB data usage per month
50Mb/s bandwidth, 5~6 TB data usage per month
OS
Ubuntu 22 LTS
Ubuntu 22 LTS
Storage
6 TB SSD Minimum, NVMe recommended
50 GB SSD Minimum, NVMe recommended
CPU
16 dedicated core
8 dedicated core
RAM
32GB minimum 64GB recommended
16GB minimum 32GB recommended
Storage (21 Feb 2024)
32 TB minimum 36 TB recommended
250 GB minimum 500 GB recommended