AutoNode allows you to spin up a node seamlessly. It will automatically make sure your validator is active and signing as well as refresh your node on hard resets.

AutoNode is not optimized for mainnet yet. This notification will be removed when AutoNode is mainnet compatible. Use "First Time Setup" to spin up your validator node!

Installing AutoNode

Step 1: Spin up your instance on AWS or other providers.

It is recommended to go with Ubuntu or Amazon Linux as your operating system.

Step 2: SSH into the machine.

AutoNode DOES NOT run with root, thus you need to login with a user that is not root.

Most cloud providers (like AWS) give you such an account as the default login. However, if you don't have a user that is not root, follow the procedures below to create one, otherwise you can just skip this part and go to Step 3.

You can choose any username you want. It will ask for a password and a password confirmation. We will also add this user to the sudo group. Please keep track of this password for future use!

sudo useradd -m <your username>
sudo passwd <your username>
sudo adduser <your username> sudo

Now login with the new username you just created.

su - <your username>

If you wish to automatically reset your node during hard resets (the --auto-reset option in step 7) your user (<your username>) must have sudo access without a passphrase. Follow instructions here to set that up.

If you don't want to do that, you can still run AutoNode! Only thing is that on hard resets, you have to do is step 6 and 7 to restart your node.

Step 3: Install AutoNode.

curl -O && chmod +x ./ && ./ && rm ./

If you are upgrading your AutoNode from a previous version the installer might ask you some questions. Answer with Y for the upgrading process to go on.

Step 4: Add or import a validator key.

New Key
Import Keystore File
Import Private Key (not recommended)
New Key
./hmy keys add validator
Import Keystore File
./hmy keys import-ks <path-to-keystore-file>
Import Private Key (not recommended)
./hmy keys import-private-key <private-key-string>

Step 5: Edit the configuration file and change the validator-addrto the ONE address created on Step 4.

./ edit-config

Note that identity must be unique or else your validator won't get created.

Save and exit the configuration by pressing Ctrl + X then Y, then by hitting enter.

Note that the ONE address has to be in quotes

Step 6: Fund your ONE address.

Step 7 : Run your validator.

./ run --auto-active --auto-reset --clean

Answer the prompts with Y or N (this process may take a minute). Feel free to exit with Ctrl+Z after your node syncs!

You can view all the commands for AutoNode with ~/ -h


If any of the commands activates a monitoring screen, you can always exit using Ctrl+Z.

1) View the log of your Harmony Monitor:

./ monitor log

2) Using TUI

./ tui run

3) View the status of your Harmony Monitor daemon:

./ monitor status

4) Restart your Harmony Monitor daemon:

./ monitor restart

Upgrade AutoNode

1) Deactivate your validator during the upgrade process

./ deactivate

2) Safely kill AutoNode & its monitor (if alive)

./ kill

3) Update AutoNode by running the install step again:

curl -O && chmod +x ./ && ./ && rm ./

4) Start up your node again but this time without the --clean option.

./ run --auto-active --auto-reset

Once your node is done syncing, AutoNode will automatically activate your validator to be elected in the next epoch!

5) (Optional) If needed, you might have to activate your validator manually, do so with:

./ activate

Cleaning Keys

1) You can cleanse your BLS (based on performance of a key) with:

./ cleanse-bls

2) Remove all keys except for keys running on your current autonode with:

./ cleanse-bls --hard

More detailed documentation can be found here.

Feel free to contribute or open issues!