Node Install

Instructions for preparation and binary set up

You will be managing three keys which will be referenced throughout this guide. These keys are the account key, the consensus key, and the ETH private key. Please keep this in mind as you proceed with the installation steps.

Installing Exocore Binary

The binary to run an Exocore node is called exocored, which stands for Exocore daemon. The binary can be downloaded from Exocore's releases page (Option 1) or built from source (Option 2).

Option 1: Downloading the Binary

The version 1.0.5 is intended for use with the exocoretestnet_233-6 version (identified by the chain-ID) of the network.

VERSION="1.0.5"
wget -O exocored_${VERSION}.tar.gz "https://github.com/ExocoreNetwork/exocore/releases/download/v${VERSION}/exocore_${VERSION}_$(uname -s)_$(uname -m | sed 's/x86_64/amd64/' | sed 's/aarch64/arm64/').tar.gz"

Extract the binary and move it somewhere within$PATH (likely /usr/bin/). Doing so will require root privileges.

tar -xvzf exocored_${VERSION}.tar.gz
mv bin/exocored /usr/bin/

Check that it is installed and reports the correct version.

exocored version
1.0.5

Option 2: Compiling from Source

Detailed instructions are available here.

Firewall

Depending on the configuration, a node will listen on many ports, such as those for the API (gRPC or REST for Cosmos, HTTP / Websocket RPC for Ethereum), Prometheus, pprof, Tendermint, etc. At the bare minimum, incoming connections should be allowed on the p2p port which defaults to 26656 over TCP. Other incoming connections (barring SSH or anything else you need to connect to the server) can be blocked for increased network layer security.

Option 1: Using UFW

# Block all incoming connections
ufw default deny incoming
# Allow SSH over port 22
ufw allow ssh
# Allow P2P incoming connections
ufw allow 26656/tcp
# Activate the firewall
ufw enable

Option 2: Using Firewalld

# Block all incoming connections
firewall-cmd --set-default-zone=drop
# Allow SSH over port 22
firewall-cmd --permanent --add-service=ssh
# Allow P2P incoming connections
firewall-cmd --permanent --add-port=26656/tcp
# Activate the firewall
firewall-cmd --reload

Initializing the Node

Once the binary is downloaded, the node needs to be initialized before it can join the network. The initialization process requires generating the validator key (even though the node may not be a validator) and the node’s configuration files.

CHAIN_ID="exocoretestnet_233-6"
MONIKER="moniker" # an ASCII alphanumerical string
HOMEDIR="/home/$USER/.exocored" # this is the default if not provided
exocored --home $HOMEDIR init $MONIKER --chain-id $CHAIN_ID
exocored --home $HOMEDIR config chain-id $CHAIN_ID

The validator's private key is stored in $HOMEDIR/config/priv_validator_key.json in plaintext. It is recommended to back this key up, since it is used by the validator to sign blocks. Alternatively, passing --recover to init will prompt for a BIP-39 mnemonic to be entered, from which the validator key is derived. In that case, the mnemonic may be backed up instead.

The public key corresponding to the validator key can be converted to the bytes32 format for use in Solidity (you might need to install jq).

exocored --output json --home $HOMEDIR keys consensus-pubkey-to-bytes | jq -r .bytes32
0xf0f6919e522c5b97db2c8255bff743f9dfddd7ad9fc37cb0c1670b480d0f9914

Keyring backend

Another type of key, known as the account key (referenced as$ACCOUNT_KEY_NAME), is used to sign transactions before they are broadcasted to the network. This key is protected by the keyring backend; it defaults to os which is not well suited for headless systems. It is recommended to change it to either file (which will use a password to protect the keys) or pass (which will use pass). Refer to the Cosmos SDK documentation for more details.

exocored --home $HOMEDIR config keyring-backend file

Add an Account

You can generate a new key for use with the network, or recover an existing one with the --recover option. This key will be linked to an account, which is used to sign transactions on the network. All account addresses on Exocore begin with "exo1," indicating they're part of Exocore.

ACCOUNT_KEY_NAME="my_key"
exocored --home $HOMEDIR keys add $ACCOUNT_KEY_NAME

- address: exo17ekpjxmvm3k2dd2wg8f6jezsnk3dn388q09tcp
  name: my_key
  pubkey: '{"@type":"/ethermint.crypto.v1.ethsecp256k1.PubKey","key":"ArhBGG18F0+kSqJksNJWoAF8NxunIgP7ySgnw622T3RR"}'
  type: local

**Important** write this mnemonic phrase in a safe place.
It is the only way to recover your account if you ever forget your password.

example anchor example account example bone example entry example breeze example divorce example wrong example turkey example joy example seek example dune example chef

Ensure you back up the mnemonic phrase in a safe place.

Seeds

All nodes connect to seed nodes so that they can find their peers. Open the $HOMEDIR/config/config.toml file to find the seeds line and edit it to match the following:

$HOMEDIR/config/config.toml

# Comma separated list of seed nodes to connect to
seeds = "[e-mail]:26656,[e-mail]:26656"

Other configuration

Changes in $HOMEDIR/config/config.toml and $HOMEDIR/config/app.toml may be made to activate and deactivate RPC servers or other features. For all nodes including validators, it is recommend to set at least minimum-gas-prices = "0.0001hua" in app.toml. For validators specifically, setting grpc.enable = true in app.toml is necessary to communicate with the price feeder.

$HOMEDIR/config/app.toml

###############################################################################
###                           Base Configuration                            ###
###############################################################################

# The minimum gas prices a validator is willing to accept for processing a
# transaction. A transaction's fees must meet the minimum of any denomination
# specified in this config (e.g. 0.25token1;0.0001token2).
minimum-gas-prices = "0.0001hua"

<! -- truncated -->

###############################################################################
###                           gRPC Configuration                            ###
###############################################################################

[grpc]

# Enable defines if the gRPC server should be enabled.
enable = true