Instructions for joining the Stargaze Mainnet
Below is the list of Stargaze mainnet id's and their current status. You will need to know the version tag for installation of the
The minimum recommended hardware requirements for running a validator for the Stargaze mainnet:
For this guide, we will be using shell variables. This will enable the use of the client commands verbatim. It is important to remember that shell commands are only valid for the current shell session, and if the shell session is closed, the shell variables will need to be re-defined.
If you want variables to persist for multiple sessions, then set them explicitly in your shell .profile, as you did for the Go environment variables.
To clear a variable binding, use
unset $VARIABLE_NAME. Shell variables should be named with ALL CAPS.
<chain-id>for the mainnet you would like to join from here. Set the
You can also set this in your
Then source it:
<moniker-name>, this can be any name of your choosing and will identify your validator in the explorer. Set the
Persistent peers will be required to tell your node where to connect to other nodes and join the network. However, the stargaze repository comes with seed values already pre-populated. To retrieve the peers for the chosen mainnet, optionally:
# Set the base repo URL for mainnet & retrieve peers
CHAIN_REPO="https://raw.githubusercontent.com/public-awesome/mainnet/main/$CHAIN_ID" && \
export PEERS="$(curl -s "$CHAIN_REPO/peers.txt")"
Seed nodes are available for your local node to quickly receive network address book entries. This will provide your node with addresses to dial and begin to build the peer book. These seed values are pre-populated within your `
$HOME/.starsd/config/app.toml, set minimum gas prices:
sed -i.bak -e "s/^minimum-gas-prices *=.*/minimum-gas-prices = \"0ustars\"/" ~/.starsd/config/app.toml
These instructions will direct you on how to initialize your node, synchronize to the network and upgrade your node to a validator.
starsd init $MONIKER_NAME --chain-id $CHAIN_ID
This will generate the following files in
curl -s https://raw.githubusercontent.com/public-awesome/mainnet/main/$CHAIN_ID/genesis.tar.gz > genesis.tar.gz
tar -C ~/.starsd/config/ -xvf genesis.tar.gz
This will replace the genesis file created using
starsd initcommand with the mainnet
Verify the genesis.json file is correct. The output of the command should return the same shasum as shown below:
jq -S -f normalize.jq ~/.starsd/config/genesis.json | shasum -a 256
Using the peer variable we set earlier, we can set these values in
sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$PEERS\"/" ~/.starsd/config/config.toml
Either create a new key pair, or restore an existing wallet for your validator:
# Create new keypair
starsd keys add <key-name>
# Restore existing stargaze wallet with mnemonic seed phrase.
# You will be prompted to enter mnemonic seed.
starsd keys add <key-name> --recover
# Query the keystore for your public address
starsd keys show <key-name> -a
<key-name>with a key name of your choosing.
You will require some Stargaze tokens to bond to your validator. To be in the active set you will need to have enough tokens to be in the top 100 validators by delegation weight. You can view the current delegator set at mintscan.io.
If you do not have any STARS for you validator you can purchase/exchange tokens on Osmosis or Emeris.
After starting the starsd daemon, the chain will begin to sync to the network. The time to sync to the network will vary depending on your setup and the current size of the blockchain, but could take a very long time. To query the status of your node:
# If not using cosmovisor, start the node with the following command in a tmux or screen session
# Query via the RPC (default port: 26657)
curl http://localhost:26657/status | jq .result.sync_info.catching_up
If this command returns
truethen your node is still catching up. If it returns
falsethen your node has caught up to the network current block and you are safe to proceed to upgrade to a validator node.
If you are syncing from the block 0 (genesis), and are not using cosmovisor through upgrades, the node will stop when reaching an upgrade height. From this point you will have to swap the
starsdbinary with the requested upgraded version to continue the sync to the top of the chain.
Once the node is synced and you have the required STARS to be in the validator set, you can initiate the upgrade.
To upgrade the node to a validator, you will need to submit a
starsd tx staking create-validator \
--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=$(starsd tendermint show-validator) \
--moniker $MONIKER_NAME \
--chain-id $CHAIN_ID \
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
It is recommended that you encrypt the backup of these files.