Full node build

Install Go and Cosmovisor

Feel free to skip this step if you already have Go and Cosmovisor.

Install Go

We will use Go v1.20.4 as example here. The code below also cleanly removes any previous Go installation.

sudo rm -rvf /usr/local/go/
wget https://golang.org/dl/go1.20.4.linux-amd64.tar.gz
sudo tar -C /usr/local -xzf go1.20.4.linux-amd64.tar.gz
rm go1.20.4.linux-amd64.tar.gz

Configure Go

Unless you want to configure in a non-standard way, then set these in the ~/.profile file.

export GOROOT=/usr/local/go
export GOPATH=$HOME/go
export GO111MODULE=on
export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin

Install Cosmovisor

We will use Cosmovisor v1.0.0 as example here.

go install github.com/cosmos/cosmos-sdk/cosmovisor/cmd/cosmovisor@v1.0.0

Install Node

Install the current version of node binary.

In order to check that the installation was successful, you can run the following command

berad --version

Which should output something like:

0.1.9-alpha

Join the network

Once the chain-id has been distributed, it is possible to join the network with the CHAIN_ID:

 export HOMEDIR=/home/user/.berad
 export KEYRING="os"
 export CHAIN_ID="artio-80085" ## (replace with the actual chain-id)
 export MONIKER="MYMONIKER"  ## (replace with your moniker)

 berad init $MONIKER --chain-id "artio-80085"

Set config file

berad config set client chain-id "$CHAIN_ID" --home "$HOMEDIR";
berad config set client keyring-backend $KEYRING --home "$HOMEDIR";

Download Genesis

wget https://github.com/berachain/networks/blob/main/testnets/artio-80085/config/genesis.json
mv genesis.json ~/.berad/config

Configure Seeds and Peers

seeds="fd8c242fbaf6166ae0fa851a03af0f7368bc0e53@15.235.212.150:26656,[e-mail]:46656,462d2746985cbffd78a669408387c5e6a6025344@65.109.70.45:56656,[e-mail]:25456,[e-mail]:25456"
peers=""
sed -i -e 's|^seeds *=.*|seeds = "'$seeds'"|; s|^persistent_peers *=.*|persistent_peers = "'$peers'"|' $HOME/.berad/config/config.toml

Update Node configs

We can use sed to update various node configuration values without having to manually edit each file - which can be a pain.

Replace the values below with your own. These commands will update the following:

• minimum_gas_prices

• pruning configs

• snapshot configs

sed -i -e "s|^minimum-gas-prices *=.*|minimum-gas-prices = \"0abgt\"|" $HOME/.berad/config/app.toml
sed -i -e "s|^pruning *=.*|pruning = \"custom\"|" $HOME/.berad/config/app.toml
sed -i -e "s|^pruning-keep-recent *=.*|pruning-keep-recent = \"113\"|" $HOME/.berad/config/app.toml
sed -i -e "s|^pruning-keep-every *=.*|pruning-keep-every = \"0\"|" $HOME/.berad/config/app.toml
sed -i -e "s|^pruning-interval *=.*|pruning-interval = \"17\"|" $HOME/.berad/config/app.toml
sed -i -e "s|^snapshot-interval *=.*|snapshot-interval = \"0\"|" $HOME/.berad/config/app.toml
sed -i -e "s|^snapshot-keep-recent *=.*|snapshot-keep-recent = \"2\"|" $HOME/.berad/config/app.toml

Updating node ports

We'll use a powerful tool called sed for this process. sed is a stream editor that can perform operations, like substitutions, on a text file.

We will specifically focus on updating the ports to use a standardized prefix for your chain. This ensures consistency and improves overall system organization. It will also allow you to run multiple chains on a single server.

Let's start by understanding what we're updating:

• proxy_app: This is the address used for inter-process communication between the ABCI application and the consensus engine.

• laddr: This is the address that your node listens on for incoming connections.

• pprof_laddr: This is the address for the profiling server to listen on.

• prometheus_listen_addr: This is the address for the Prometheus metrics server to listen on.

• address: These are various addresses that your node may use to listen for different types of connections.

Set Your Chain and Port Prefix

Your chain in this case is BeraChain. For Berachain, we want to set the port prefix as 254. The port prefix will be used to replace the first 2 or 3 digits of the original ports.

# Set the prefix 
export PREFIX=254

Update config.toml

Next, we will update the config.toml file. For 5-digit ports, the first 3 digits will be replaced. Here is how to calculate the new port values and update the config.toml file:

PROXY_APP_PORT=$(echo 26658 | awk -v prefix=$PREFIX '{print prefix substr($0,4)}')
LADDR_PORT1=$(echo 26657 | awk -v prefix=$PREFIX '{print prefix substr($0,4)}')
LADDR_PORT2=$(echo 26656 | awk -v prefix=$PREFIX '{print prefix substr($0,4)}')
PPROF_LADDR_PORT=$(echo 26660 | awk -v prefix=$PREFIX '{print prefix substr($0,4)}')
PROMETHEUS_LISTEN_PORT=$(echo 26660 | awk -v prefix=$PREFIX '{print prefix substr($0,4)}')

sed -i.bak -e "\
s%^proxy_app = \"tcp://127.0.0.1:26658\"%proxy_app = \"tcp://127.0.0.1:$PROXY_APP_PORT\"%; \
s%^laddr = \"tcp://127.0.0.1:26657\"%laddr = \"tcp://0.0.0.0:$LADDR_PORT1\"%; \
s%^pprof_laddr = \"localhost:6060\"%pprof_laddr = \"localhost:$PPROF_LADDR_PORT\"%; \
s%^laddr = \"tcp://0.0.0.0:26656\"%laddr = \"tcp://0.0.0.0:$LADDR_PORT2\"%; \
s%^prometheus_listen_addr = \":26660\"%prometheus_listen_addr = \":$PROMETHEUS_LISTEN_PORT\"%" \
$HOME/.berad/config/config.toml

Update app.toml

For 4-digit ports, the first 2 digits will be replaced. Here is how to calculate the new port values and update the app.toml file:

ADDRESS_PORT1=$(echo 1317 | awk -v prefix=$PREFIX '{print prefix substr($0,3)}')
ADDRESS_PORT2=$(echo 8080 | awk -v prefix=$PREFIX '{print prefix substr($0,3)}')
ADDRESS_PORT3=$(echo 9090 | awk -v prefix=$PREFIX '{print prefix substr($0,3)}')
ADDRESS_PORT4=$(echo 9091 | awk -v prefix=$PREFIX '{print prefix substr($0,3)}')

sed -i.bak -e "\
s%^address = \"tcp://0.0.0.0:1317\"%address = \"tcp://0.0.0.0:$ADDRESS_PORT1\"%; \
s%^address = \":8080\"%address = \":$ADDRESS_PORT2\"%; \
s%^address = \"0.0.0.0:9090\"%address = \"0.0.0.0:$ADDRESS_PORT3\"%; \
s%^address = \"0.0.0.0:9091\"%address = \"0.0.0.0:$ADDRESS_PORT4\"%" \
$HOME/.berad/config/app.toml

In app.toml also check:

# Miner config
[polaris.polar.miner]
# The address to which mining rewards will be sent
etherbase = "YOURADDRESS HERE"

# Extra data included in mined blocks
extra-data = "0x"

# Chain config
[polaris.polar.chain]
chain-id = "80085"

In client.toml check:

# The network chain ID
chain-id = "artio-80085"

Genesis file check:

Run the following CLI command against your genesis.json file:

sha256sum genesis.json

Ensure that the output matches the following hash:

109c5cb418c209c8a7974d328a66bc501529a94ca24b2b3df1606a464405f3ef

If you receive a different hash, please download the final genesis.json from here: https://github.com/berachain/networks/blob/main/testnets/artio-80085/config/genesis.json Setup cosmovisor

Follow the Setup Cosmovisor instructions to setup cosmovisor and start the node.

Create (or restore) a local key pair

Either create a new key pair or restore an existing wallet for your validator:

# Create new keypair
berad keys add YOURKEY

# Restore existing juno wallet with mnemonic seed phrase.
# You will be prompted to enter mnemonic seed.
berad keys add YOURKEY --recover

# Query the keystore for your public address
berad keys show YOURKEY -a

After creating a new key, the key information and seed phrase will be shown. It is essential to write this seed phrase down and keep it in a safe place. The seed phrase is the only way to restore your keys.

Upgrade to a validator

Do not attempt to upgrade your node to a validator until the node is fully in sync as per the previous step.

To upgrade the node to a validator, you will need to submit a create-validator transaction:

berad tx staking create-validator \
  --amount 500000000000udym \
  --commission-max-change-rate "0.1" \
  --commission-max-rate "0.20" \
  --commission-rate "0.05" \
  --min-self-delegation "1" \
  --details "validators write bios too" \
  --pubkey=$(dymd tendermint show-validator) \
  --moniker $MONIKER_NAME \
  --chain-id froopyland_100-1 \
  --gas-prices 0.25udym \
  --from <KEYNAME>

The above transaction is just an example. There are many more flags that can be set to customise your validator, such as your validator website, or keybase.io id, etc. To see a full list:

berad tx staking create-validator --help

Backup critical files

There are certain files that you need to backup to be able to restore your validator if, for some reason, it damaged or lost in some way. Please make a secure backup of the following files located in ~/.dymension/config/:

• priv_validator_key.json

• node_key.json

It is recommended that you encrypt the backup of these files.