1 of 18

4. Installing & Updating

Installing A Node

Using Node Binary

As per instructions on the cloud guides, the host needs to open up port 9000 for blockchain consensus messages and port 6000 for blockchain state syncing. Other ports are NOT necessary for syncing and should NOT be opened to the internet if you are staking only.

9000 port is used for blockchain consensus messages (base port)
6000 port is used for blockchain state syncing (base port - 3000)
9500 port is used for SDK RPC service (base port + 500)
9800 port is used for Websocket service (base port + 800)

The 9500, 9800 ports are only listened by localhost 127.0.0.1 by default.

1. Download Node Binary

Before we proceed to next steps we need to download the node binary first:

Check the node binary version that was downloaded:

The below explain the different method the node binary can be used. Option 1 is what being used when setting up systemd ().

If you choose another method make sure to use the correct command line

Option 1: Setup Using Config File (recommended)

All the start options can be persisted and loaded from a single config file. To start a node, the following steps are also available**:**

Dump the default config.
Customize the config file.
Run harmony node with the config file.

Dump the Default Config File

A file harmony.conf is created and the default node options are set in the file in TOML formatting. Here is an example:

The content of the config file can be modified for custom node start up command.

For example, to open the public HTTP RPCs, change the field IP under [HTTP] tag to "0.0.0.0":

To run harmony internal nodes (or Foundational Node FN), under legacy mode instead of staking mode, change the field NoStaking under [General] tag to true:

To enable streamsync, modify the below two sections (Experimental. use at your own risk)

Stream Sync is the new harmony P2P syncing method allowing to get rid of the previous sync via DNS causing issue when the DNS

Start the node with Config File

Harmony node binary is able to start with options provided by the config file:

The values stored in the config file will be read and parsed to harmony as node start options.

Option 2: Setup Using Flag Parsing

You can run your node binary using flag parsing:

A full list of active flags as well as examples can be accessed through running the binary with --help option:

Output:

Option 3: Setup Using Flag Parsing and a Config file combined

If both config file and flag is provided, the node option stored in config file will be override by the values given in flag.

For example, In config file harmony.conf, HTTP server is enabled, and is open to public:

And a flag is also provided during the node start command to disable the HTTP server:

In this case, the command line flags will override the settings in the config file and thus the HTTP server is disabled.

The above steps would have you started the node, please CTRL+C, so you can continue with step 2.

Non-Validating/Explorer Nodes

A Non-validating Node is a node that does not join the consensus.

Check for Explorer Node requirements.

Check for instructions on how to sync your node in archival mode.

Keep in mind that the storage space used increases around ~50+ GB per month on s0 due to staking transaction being stored. Other shard should take around 25GB per month. Please plan your storage space accordingly.

The following steps assume the node is connected to mainnet on shard 0, which is required for all exchanges.

If you are using the config file, which is the recommended way to configure your node, change the settings to the ones below:

NoStaking = true will verify if the BLS keys in your .hmy/blskeys folder are part of the original Foundational Node (FN) keys. For explorer, you will need to add in the folder dummy BLS/pass files and remove all others

IsBeaconArchival flag is applicable to explorer node only. For shard 1/2/3 the beacon shard 0 doesn't need to be in archival mode. So to save space, the recommendation is to set to false. For shard 0 explorer node, IsArchival flag will determine if the database is in archival mode or not.

DataDir (or --db_dir below for cli flag) is the folder where the blockchain data will be store (ie location of harmony_db_0)

Change harmony.conf file and update the RPC Rate Limit to 50000:

7. Start Systemd Service

Alternatively, you can also run it using flag parsing:

2. Setup Systemd

On this example, we will be installing the harmony daemon for user harmony on its home directory. Daemon will be configured with sudobut it will run with the harmonyuser at the end.

Create the harmony.service file:

Add the content below to the file and save it. Change User to the local user you will be running the daemon and also WorkingDirectory to the home directory where you downloaded the harmony binary file previously. Parameter ExecStart needs to point to this same directory. On the example below we will be running the harmony binary using the harmony.conf file.

Give the necessary permissions to run the daemon service, enable it and start it:

If you want to check the status of the daemon you can use:

To restart, or stop the service daemon you can run:

To check your node follow instructions on .

(Deprecated) Using AutoNode

AutoNode allows you to spin up a node seamlessly and automate common validator actions.

Install & Run Update Monitor BLS Key Management Collect Rewards Maintenance Troubleshoot Extra

Contribute!

Want to add a feature to AutoNode? Feel free to contribute to the open-sourced repo here!

Install & Run

Quick start to running a Harmony Validator.

This option is deprecated and is not supported anymore. Please setup your node .

All commands for auto-node

Update

Run the latest AutoNode!

Checking for AutoNode updates

AutoNode will quickly check for an update on each execution of the auto-node command. If there is an update you will see the following message:

Updating AutoNode

You will need to briefly stop your node to execute an update. Updates should be fast.

Step 0: (Optional) Stop Auto

Kill your AutoNode with the following command:

Note that if you are still elected and signing, AutoNode will ask for you to confirm before killing your node.

Step 1: Start the update

You can start the update with the following command:

Note that AutoNode will check to make sure the harmony node is stopped. If it detects that the harmony node is still running, It will ask to kill itself before starting the update.

You can also re-run the install script from step 3 of the Install & Run script to update AutoNode

Step 2: Restart/Rerun your AutoNode

Make sure to restart your AutoNode after the update to resume validating or operations. For a validator, it will most likely be:

DO NOT restart AutoNode with the --clean or --fast-sync as it will probably regress your block hight (since it edits the DB files).

Updating `hmy` CLI

For your convenience, AutoNode wraps the hmy You can update it with the following command:

Monitor

Track your node's status with AutoNode.

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

BLS Key Management

Manage & re-use your BLS keys.

Currently, all BLS keys MUST have the same passphrase. A feature to improve this is in the works.

BLS key(s) location

You can find the path to your BLS keys directory (used by the harmony node) with the following command:

By default, this should be ~/.hmy/blskeys

Any BLS key present in that directory will be attempted to be used when launching the node. This means that all BLS keys in the said directory need to be for the same shard. Moreover, any .passfiles will also be attempted to be used when launching a node

BLS key for shard

This assumes AutoNode has been initialized.

You can find which shard a public BLS key belongs to with the following command:

Cleanse BLS key(s) from Validator

You can automatically cleanse your validator of BLS key(s) that have not signed any blocks in the current epoch with the following command:

You can cleanse all BLS key(s) that are not on the same shard as the BLS key(s) used by the current harmony node's shard with the following command:

You can also cleanse the BLS key(s) that are not being used by the current harmony node with the following command:

Remove BLS key from Validator

You can remove an explicit BLS key from your validator with the following command:

Collect Rewards

Get your ONEs for validating!

1. Sending a Collect Rewards Transaction

You can simply collect rewards for your validator with the following command:

auto-node collect-rewards

2. (Optional) Send funds to your 'main' wallet

If you have followed the recommended method of creating a wallet just for running a validator, you can send funds to your 'main' wallet with the following steps.

First, get the balance of your validator wallet with the following command:

Note the shard 0 balance, this is where the rewards get deposited. Next, transfer the funds to your 'main' wallet with the following command:

Substitute <main-wallet-address> with the ONE address of your main wallet. Substitute <amount> with how much you want to transfer from your validator wallet.

Maintenance

Steps for maintaining your node with AutoNode.

Edit Validator config

After your validator is created, you can edit your validator config with the following command:

This will open up a Nano session to edit the config. After you do your edits, save it by pressing Ctrl+X then Y.

After you finish editing, you will be asked to update the config on-chain. If you say yes, AutoNode will send an edit validator transaction to update your validator.

Note that the following are the ONLY fields that can be edited on-chain: "details", "identity", "name", "security-contact", "website", "max-total-delegation", "min-self-delegation", "rate"

Deactivate Validator

You can deactivate your validator if you would like to not get elected the following epoch. You can do so with the following command:

Activate Validator

When you are ready to get elected and sign the following epoch, you can activate your validator with the following command:

Inspect the Harmon Node logs

Node logs are saved in the following directory: $HOME/harmony_node/latest

You can view the logs with the following command:

Inspect the Harmony Node service logs

The Harmony Node is ran as a , you can inspect the logs for the service with the following command:

Inspect the AutoNode monitor service logs

Similar to the Harmony Node, the monitor is ran as a service and you can inspect the logs for the service with the following command:

Extra

Some optional extras that you may find useful.

Using wallet passphrase from file

We do not recommend storing your passphrase in plain text. If you choose to, you can have AutoNode import your wallets passphrase from a file. First, save the passphrase using the following convention:

Then, move the saved passphrase into the harmony wallet passphrase directory using the following command:

Then, when you run AutoNode with

(deprecated) Using Node.sh

This option is deprecated and is not supported anymore. Please setup your node .

1. Download Node.sh

Upgrading A Node

Using Node Binary

Validator Nodes

1. Backup Files

Create a folder called "

Using AutoNode (deprecated)

This option is deprecated and is not supported anymore. Please update your node Using Node Binary.

For instructions on how to update Using AutoNode click here.

Using Node.sh (deprecated)

This option is deprecated and is not supported anymore. Please update your node .

1. Stop Systemd Service

Checking A Node

1. Check Node Running Version

To check the node version that is running, run the command below:

2. Check if Node is Syncing

1. To check if your node is syncing properly, run the command below and check that the block height of the shard(s).

Harmony relies on a beacon shard chain (aka shard 0) to facilitate cross shard transaction. For the node to be fully working both your non shard 0 and shard 0 needs to be fully synced.

2. Before continuing, check if your node is fully synced using an external endpoint. Replace parameter --node with the enpoint you want to compare with. Check the examples below for shard 0 on mainnet and testnet. Just change the edpoints to do the comparison with other shards.

For a complete reference of all available enpoints on both mainnet and testnet, please click . Alternatively you can use the for a visual comparison.

3. Verify if blocks shown on steps 1 and 2 are closer or equal to each other. If so, your node should have caught up!

Using Node Binary

9000 port is used for blockchain consensus messages (base port)
6000 port is used for blockchain state syncing (base port - 3000)
9500 port is used for SDK RPC service (base port + 500)
9800 port is used for Websocket service (base port + 800)

The 9500, 9800 ports are only listened by localhost 127.0.0.1 by default.

1. Download Node Binary

Before we proceed to next steps we need to download the node binary first:

Check the node binary version that was downloaded:

The below explain the different method the node binary can be used. Option 1 is what being used when setting up systemd ().

If you choose another method make sure to use the correct command line

Option 1: Setup Using Config File (recommended)

All the start options can be persisted and loaded from a single config file. To start a node, the following steps are also available**:**

Dump the default config.
Customize the config file.
Run harmony node with the config file.

Dump the Default Config File

A file harmony.conf is created and the default node options are set in the file in TOML formatting. Here is an example:

The content of the config file can be modified for custom node start up command.

For example, to open the public HTTP RPCs, change the field IP under [HTTP] tag to "0.0.0.0":

To run harmony internal nodes (or Foundational Node FN), under legacy mode instead of staking mode, change the field NoStaking under [General] tag to true:

To enable streamsync, modify the below two sections (Experimental. use at your own risk)

Stream Sync is the new harmony P2P syncing method allowing to get rid of the previous sync via DNS causing issue when the DNS

Start the node with Config File

Harmony node binary is able to start with options provided by the config file:

The values stored in the config file will be read and parsed to harmony as node start options.

Option 2: Setup Using Flag Parsing

You can run your node binary using flag parsing:

A full list of active flags as well as examples can be accessed through running the binary with --help option:

Output:

Option 3: Setup Using Flag Parsing and a Config file combined

If both config file and flag is provided, the node option stored in config file will be override by the values given in flag.

For example, In config file harmony.conf, HTTP server is enabled, and is open to public:

And a flag is also provided during the node start command to disable the HTTP server:

In this case, the command line flags will override the settings in the config file and thus the HTTP server is disabled.

The above steps would have you started the node, please CTRL+C, so you can continue with step 2.

Non-Validating/Explorer Nodes

A Non-validating Node is a node that does not join the consensus.

Check for Explorer Node requirements.

Check for instructions on how to sync your node in archival mode.

The following steps assume the node is connected to mainnet on shard 0, which is required for all exchanges.

If you are using the config file, which is the recommended way to configure your node, change the settings to the ones below:

DataDir (or --db_dir below for cli flag) is the folder where the blockchain data will be store (ie location of harmony_db_0)

Change harmony.conf file and update the RPC Rate Limit to 50000:

7. Start Systemd Service

Alternatively, you can also run it using flag parsing:

2. Setup Systemd

On this example, we will be installing the harmony daemon for user harmony on its home directory. Daemon will be configured with sudobut it will run with the harmonyuser at the end.

Create the harmony.service file:

Give the necessary permissions to run the daemon service, enable it and start it:

If you want to check the status of the daemon you can use:

To restart, or stop the service daemon you can run:

To check your node follow instructions on .

Examples usage:

# start a validator node with default bls folder (default bls key files in ./.hmy/blskeys)
    ./harmony

# start a validator node with customized bls key folder
    ./harmony --bls.dir [bls_folder]

# start a validator node with open RPC endpoints and customized ports
    ./harmony --http.ip=0.0.0.0 --http.port=[http_port] --ws.ip=0.0.0.0 --ws.port=[ws_port]

# start an explorer node
    ./harmony --run=explorer --run.shard=[shard_id]

# start a harmony internal node on testnet
    ./harmony --run.legacy --network testnet

Usage:
  harmony [flags]
  harmony [command]

Available Commands:
  config      dump or update config
  dumpdb      dump a snapshot db.
  help        Help about any command
  version     print version of the harmony binary

Flags:
      --bls.dir string                     directory for BLS keys (default "./.hmy/blskeys")
      --bls.keys strings                   a list of BLS key files (separated by ,)
      --bls.kms                            enable BLS key decryption with AWS KMS service
      --bls.kms.config string              json config file for KMS service (region and credentials)
      --bls.kms.src string                 the AWS config source (region and credentials) for KMS service (shared, prompt, file) (default "shared")
      --bls.pass                           enable BLS key decryption with passphrase (default true)
      --bls.pass.file string               the pass file used for BLS decryption. If specified, this pass file will be used for all BLS keys
      --bls.pass.save                      after input the BLS passphrase from console, whether to persist the input passphrases in .pass file
      --bls.pass.src string                source for BLS passphrase (auto, file, prompt) (default "auto")
      --bootnodes strings                  a list of bootnode multiaddress (delimited by ,)
  -c, --config string                      load node config from the config toml file.
      --consensus.aggregate-sig            (multi-key) aggregate bls signatures before sending (default true)
      --datadir string                     directory of chain database (default "./")
      --dns.port int                       dns sync remote server port (default 6000)
      --dns.server-port int                dns sync local server port (default 6000)
      --dns.zone string                    use customized peers from the zone for state syncing
  -h, --help                               help for harmony
      --http                               enable HTTP / RPC requests (default true)
      --http.auth-port int                 rpc port to listen for auth HTTP requests (default 9501)
      --http.ip string                     ip address to listen for RPC calls. Use 0.0.0.0 for public endpoint (default "127.0.0.1")
      --http.port int                      rpc port to listen for HTTP requests (default 9500)
      --http.rosetta                       enable HTTP / Rosetta requests
      --http.rosetta.port int              rosetta port to listen for HTTP requests (default 9700)
      --log.console                        output log to console only
      --log.dir string                     directory path to put rotation logs (default "./latest")
      --log.max-size int                   rotation log size in megabytes (default 100)
      --log.name string                    log file name (e.g. harmony.log) (default "harmony.log")
      --log.rotate-count int               maximum number of old log files to retain
      --log.rotate-max-age int             maximum number of days to retain old log files
  -v, --log.verb int                       logging verbosity: 0=silent, 1=error, 2=warn, 3=info, 4=debug, 5=detail (default 3)
      --log.verbose-prints strings         debugging feature. to print verbose internal objects as JSON in log file. available internal objects: config (default [config])
      --metrics                            flag required to enable the eth metrics
      --metrics.expensive                  flag required to enable the expensive eth metrics
  -n, --network string                     network to join (mainnet, testnet, pangaea, localnet, partner, stressnet, devnet) (default "mainnet")
      --p2p.disc.concurrency int           the pubsub's DHT discovery concurrency num (default with raw libp2p dht option)
      --p2p.ip string                      ip to listen for p2p protocols (default "0.0.0.0")
      --p2p.keyfile string                 the p2p key file of the harmony node (default "./.hmykey")
      --p2p.no-private-ip-scan             disable scanning of private ip4/6 addresses by DHT
      --p2p.port int                       port to listen for p2p protocols (default 9000)
      --p2p.security.max-conn-per-ip int   maximum number of connections allowed per remote node, 0 means no limit (default 10)
      --p2p.security.max-peers int         maximum number of peers allowed, 0 means no limit (default 10)
      --pprof                              enable pprof profiling
      --pprof.addr string                  listen address for pprof (default "127.0.0.1:6060")
      --pprof.profile.names strings        a list of pprof profile names (separated by ,) e.g. cpu,heap,goroutine
      --prometheus                         enable HTTP / Prometheus requests (default true)
      --prometheus.ip string               ip address to listen for prometheus service (default "0.0.0.0")
      --prometheus.port int                prometheus port to listen for HTTP requests (default 9900)
      --prometheus.push                    enable prometheus pushgateway
      --prometheus.pushgateway string      prometheus pushgateway URL (default "https://gateway.harmony.one")
      --rpc.ratelimit int                  the number of requests per second for RPCs (default 1000)
      --rpc.ratelimiter                    enable rate limiter for RPCs (default true)
      --run string                         run node type (validator, explorer) (default "validator")
      --run.archive                        run shard chain in archive mode
      --run.beacon-archive                 run beacon chain in archive mode
      --run.legacy                         whether to run node in legacy mode
      --run.offline                        run node in offline mode
      --run.shard int                      run node on the given shard ID (-1 automatically configured by BLS keys) (default -1)
      --sharddata.cache_size int           local cache storage size (MB) (default 512)
      --sharddata.cache_time int           local cache save time (minute) (default 10)
      --sharddata.disk_count int           the count of disks you want to storage block data (default 8)
      --sharddata.enable                   whether use multi-database mode of levelDB
      --sharddata.shard_count int          the count of shards you want to split in each disk (default 4)
      --sync                               Enable the stream sync protocol (experimental feature)
      --tracing                            indicates if full transaction tracing should be enabled
      --txpool.accountslots int            number of executable transaction slots guaranteed per account (default 16)
      --txpool.allowedtxs string           file of allowed transactions (default "./.hmy/allowedtxs.txt")
      --txpool.blacklist string            file of blacklisted wallet addresses (default "./.hmy/blacklist.txt")
      --txpool.globalslots int             maximum global number of non-executable transactions in the pool (default 5120)
      --txpool.locals string               file of local wallet addresses (default "./.hmy/locals.txt")
      --txpool.rosettafixfile string       file of rosetta fix file
  -V, --version                            display version info
      --ws                                 enable websocket endpoint (default true)
      --ws.auth-port int                   port for websocket auth endpoint (default 9801)
      --ws.ip string                       ip endpoint for websocket. Use 0.0.0.0 for public endpoint (default "127.0.0.1")
      --ws.port int                        port for websocket endpoint (default 9800)

Use "harmony [command] --help" for more information about a command.

Troubleshoot

Some steps for troubleshooting your AutoNode.

If you encounter any issue you cannot solve, feel free to reach out to us at [email protected]. Alternatively you can open a Github issue here.

Inspect AutoNode logs

All AutoNode generated logs are saved in $HOME/.hmy when you execute the following command:

You should see 2 files, autonode_monitor.log and autonode_node.log. Inspect those two files with your favorite command-line editor (i.e: vim) to see where things might have gone wrong.

You might also find it useful to inspect the Harmony Node logs. You can do so with the following command:

You can change the vim part of the command for your favorite text editor.

Node failed to start

A symptom of this is seeing an error to connect to http://localhost:9500/. You can inspect what went wrong with the following command:

A common issue is that your machine will not have enough disk space. You can check your disk space usage with the following command:

If your use% is at 95-100% and your node failed to start, you probably have insufficient disk space. Look into how to increase your disk space on your cloud provider.

You can also try to reboot your AutoNode with:

Substitute <params> with whatever run params you want to use.

Fixing Signing Issues

Sometimes the Harmony Node may have some signing issues. In this case, we have found it best to just restart the Node. You can do so by first killing AutoNode:

Then restarting AutoNode with whatever your initial run command was. For example, one could run it with:

DO NOT re-run with the --clean or --fast-sync options as they will most likely regress your block height to the last snapshotted DB.

Restart the Harmony Node

You can restart the Harmony Node service with the following command:

You can check the status of the service with the following command:

You can fetch the Harmony Node version with the following command:

Restart the AutoNode Monitor

You can restart the monitor service with the following command:

You can check the status of the service with the following command:

Re-Authenticating your validator wallet

If your encrypted passphrase for your validator is ever invalidated, you can re-encrypt and save it with the following command:

Optimize Operating System

You can choose to optimize your operating system for running a harmony node. The optimizations, or tunes, are made to keep your node safe but also lifts some default restrictions. Here is the command to tune your OS with AutoNode:

This will tune the kernel and the --save option will make it persistant. If you do not have the --save option, the tunes will only last untill the system is rebooted (by you or your VPS). Note that all the tunes will be displayed and confirmation asked before applying the tunes.

You can also tune/optimize your network settings with the following command:

Restoring Operating System from Optimization

If you want to revert the optimization/tune applied by AutoNode, you can do so by running the following command:

Note that you can run the command muliple times to restore previous tunes chronologically. Moveover, the restored tunes will be displayed and a confirmation will be asked before applying the restoreation.

Fresh Install

First, remove all of the AutoNode files. You can do so with the following command:

After, you can re-install AutoNode from fresh using the steps in the Install & Run section.

4. Installing & Updating

Installing A Node

Using Node Binary

hashtag1. Download Node Binary

hashtagOption 1: Setup Using Config File (recommended)

hashtagDump the Default Config File

hashtagStart the node with Config File

hashtagOption 2: Setup Using Flag Parsing

hashtagOption 3: Setup Using Flag Parsing and a Config file combined

hashtagNon-Validating/Explorer Nodes

hashtag7. Start Systemd Service

hashtag2. Setup Systemd

(Deprecated) Using AutoNode

hashtagContribute!

Install & Run

Update

hashtagChecking for AutoNode updates

hashtagUpdating AutoNode

hashtagStep 0: (Optional) Stop Auto

hashtagStep 1: Start the update

hashtagStep 2: Restart/Rerun your AutoNode

hashtagUpdating hmy CLI

Monitor

hashtag

BLS Key Management

hashtagBLS key(s) location

hashtagBLS key for shard

hashtagCleanse BLS key(s) from Validator

hashtagRemove BLS key from Validator

Collect Rewards

hashtag1. Sending a Collect Rewards Transaction

hashtag2. (Optional) Send funds to your 'main' wallet

Maintenance

hashtagEdit Validator config

hashtagDeactivate Validator

hashtagActivate Validator

hashtagInspect the Harmon Node logs

hashtagInspect the Harmony Node service logs

hashtagInspect the AutoNode monitor service logs

Extra

hashtagUsing wallet passphrase from file

(deprecated) Using Node.sh

hashtag1. Download Node.sh

Upgrading A Node

Using Node Binary

hashtagValidator Nodes

hashtag1. Backup Files

Using AutoNode (deprecated)

Using Node.sh (deprecated)

hashtag1. Stop Systemd Service

Checking A Node

hashtag1. Check Node Running Version

hashtag2. Check if Node is Syncing

Installing A Node

(Deprecated) Using AutoNode

hashtagContribute!

Update

hashtagChecking for AutoNode updates

hashtagUpdating AutoNode

hashtagStep 0: (Optional) Stop Auto

hashtagStep 1: Start the update

hashtagStep 2: Restart/Rerun your AutoNode

hashtagUpdating hmy CLI

BLS Key Management

hashtagBLS key(s) location

hashtagBLS key for shard

hashtagCleanse BLS key(s) from Validator

hashtagRemove BLS key from Validator

Install & Run

hashtagStep 1: Spin up your instance on AWS or other providersarrow-up-right

hashtagStep 2: SSH into the machine

hashtagStep 2.5: (Optional) Create a new user

hashtagStep 3: Install AutoNode

hashtagStep 3.5: (Optional) Update your shell

hashtagStep 4: Add or import a Validator Key

hashtagStep 5: Run AutoNode & start your Validator

hashtagStep 5.5: (Optional) Create your validator after the initial run

Maintenance

hashtagEdit Validator config

hashtagDeactivate Validator

1. Download Node Binary

Option 1: Setup Using Config File (recommended)

Dump the Default Config File

Start the node with Config File

Option 2: Setup Using Flag Parsing

Option 3: Setup Using Flag Parsing and a Config file combined

Non-Validating/Explorer Nodes

7. Start Systemd Service

2. Setup Systemd

Contribute!

Checking for AutoNode updates

Updating AutoNode

Step 0: (Optional) Stop Auto

Step 1: Start the update

Step 2: Restart/Rerun your AutoNode

Updating `hmy` CLI

BLS key(s) location

BLS key for shard

Cleanse BLS key(s) from Validator

Remove BLS key from Validator

1. Sending a Collect Rewards Transaction

2. (Optional) Send funds to your 'main' wallet

Edit Validator config

Deactivate Validator

Activate Validator

Inspect the Harmon Node logs

Inspect the Harmony Node service logs

Inspect the AutoNode monitor service logs

Using wallet passphrase from file

1. Download Node.sh

Validator Nodes

1. Backup Files

1. Stop Systemd Service

1. Check Node Running Version

2. Check if Node is Syncing

Contribute!

Checking for AutoNode updates

Updating AutoNode

Step 0: (Optional) Stop Auto

Step 1: Start the update

Step 2: Restart/Rerun your AutoNode

Updating `hmy` CLI

BLS key(s) location

BLS key for shard

Cleanse BLS key(s) from Validator

Remove BLS key from Validator

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

Step 2: SSH into the machine

Step 2.5: (Optional) Create a new user

Step 3: Install AutoNode

Step 3.5: (Optional) Update your shell

Step 4: Add or import a Validator Key

Step 5: Run AutoNode & start your Validator

Step 5.5: (Optional) Create your validator after the initial run

Edit Validator config

Deactivate Validator

Activate Validator

Inspect the Harmon Node logs

Inspect the Harmony Node service logs

Inspect the AutoNode monitor service logs

1. Check Node Running Version

2. Check if Node is Syncing

1. Download Node.sh

1. Stop Systemd Service

2. Setup Node.sh

3. Setup Systemd

3. Download Node.sh

4. Restart Systemd Service

Using wallet passphrase from file

1. Sending a Collect Rewards Transaction

2. (Optional) Send funds to your 'main' wallet

Validator Nodes

1. Backup Files

2. Download Node Binary

3. Restart Systemd Service

Non-Validating/Explorer Nodes

2) TUI

3) Harmony Node

Extra

1. Restart monitor