Notes on the node setup section
Remember to read our [Before I Set a Validator Up]/harmony/companion/new/before) section and make a plan before starting here. You'll want to have a non-root user account (with sudo access to run root commands is ok!) created and the ~/harmony directory setup.
We won't cover multiple BLS Keys here as they aren't needed to get started. Make one and add one to start (worry about BLS keys when we get there).
If you're doing it "The Easy Node Way" and have already made a folder, always remember to change into your harmony directory before running commands!
Use the curl command provided to download and install HMY CLI on your Linux OS inside of your ~/harmony folder.
curl -LO https://harmony.one/hmycli && mv hmycli hmy && chmod +x hmy
Verify it's installed by running this command.
./hmy --node="https://api.s0.t.hmny.io" cookbook
The Output is a reference for commands you an perform now with the HMY CLI.
Setting up BLS Keys
Here's our suggestions on how to create BLS Keys for your server.
This covers creation of your BLS Key(s) that you decided on before starting the guide. We encourage you to run one on shards 1-3 instead of just 0.
Rclone only needs to be run one time per shard database. It will get your database as close to updated as possible (most likely end of last epoch) and then later the harmony service will finish the synchronization before you send your create my validator command.
This section walks you through installing rclone.
This section shows you where your file will be stored and gives you a command to create the file. No changes needed.
These sections give you the command to download the databases for the shards you'd like. If you're on shard 1-3 you will have 2 commands to run.
Archival Node can be ignored if you're not setting up an Archival Node (you wouldn't be here for that!).
This is the method you currently want to use. Skip Autonode & Node.sh for you setup. Installation is pretty standard here, no changes just run the curl command to install harmony in your folder.
Use the command you'd like to install the harmony application. Run this inside your ~/harmony folder.
You will want to setup a configuration file to use with your service in the next step. The default configuration file works for 99.9% of administrators.\
You can create the service as per normal but some configuration changes may be required on this step. You'll want to modify the harmony service file below to meet your installation & configuration needs.
sudo nano /etc/systemd/system/harmony.service
sudo vi /etc/systemd/system/harmony.service
- Line 9 - Set this to the account name you're using
- Line 10 & 11 - If you used a harmony subdirectory as suggested set them up as shown below
[Unit]Description=Harmony daemonAfter=network-online.target[Service]Type=simpleRestart=alwaysRestartSec=1User=[myUserName]WorkingDirectory=/home/[myUserName]/harmonyExecStart=/home/[myUserName]/harmony/harmony -c harmony.confSyslogIdentifier=harmonyStartLimitInterval=0LimitNOFILE=65536LimitNPROC=65536[Install]WantedBy=multi-user.target
Add your user account name in place of [myUserName] in the commands in this guide.
At this point you can continue with the rest of the regular Official Harmony Guide.
When you run the 3 commands after you edit the above & create the systemd file you may get an error if you check your service as you haven't loaded a wallet yet. In the next section you'll create or add an existing wallet as your official validator address.
You won't need to update a node at this point. However when you're ready to upgrade see our Upgrade Script section if you'd like to script the upgrade process.
There's a few commands you're going to use here regularly to check things out, however if you set up our Stats Script you can use that to check your status and use these sparingly as needed.
One command you'll want to run from time to time on both nodes to verify they are in sync is known as the "BINGO" command around the Harmony community. This command shows you a live view of the end of your log and prints every time it finds a block signature. You won't see this if you are not elected! To check for BINGO run the following command:
tail -f latest/zerolog-harmony.log | grep BINGO