Joining Mainnet

Mainnet binary version
The correct version of the binary for mainnet at genesis is v1.0.0. Its release page can be found here.
Mainnet chain-id
Below is the list of Juno mainnet id's and their current status. You will need to know the version tag for installation of the junod binary. 
chain-id
Description
Status
Block Start
Block Finish
juno-1
This is the first chain-id from the genesis event.
current
0
N/A
Recommended Minimum Hardware
The minimum recommended hardware requirements for running a validator for the Juno mainnet are:
Chain-id
Requirements
juno-1
​
4 Cores (1.4Ghz minimum)
4GB RAM
150GB of storage (SSD or NVME)
Note that the mainnet will accumulate data as the blockchain continues. This means that you will need to expand your storage as the blockchain database gets larger with time.
junod Installation
To get up and running with the junod binary, please follow the instructions here.
Mainnet will initially use the v1.0.0 tag on GitHub. Make sure you build this version of the Juno binary.
Configuration of Shell Variables
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.
Choose the required mainnet chain-id
Choose the <chain-id> for the mainnet you would like to join from here. Set the CHAIN_ID:
1
CHAIN_ID=<chain-id>
2
​
3
# Example
4
CHAIN_ID=juno-1
Copied!
You can also set this in your .profile file:
1
export CHAIN_ID=juno-1
Copied!
Then source it:
1
source .profile
Copied!
Set your moniker name
Choose your <moniker-name>, this can be any name of your choosing and will identify your validator in the explorer. Set the MONIKER_NAME:
1
MONIKER_NAME=<moniker-name>
2
​
3
# Example
4
MONIKER_NAME="Validatron 9000"
Copied!
Set persistent peers
Persistent peers will be required to tell your node where to connect to other nodes and join the network. To retrieve the peers for the chosen mainnet:
1
# Set the base repo URL for mainnet & retrieve peers
2
CHAIN_REPO="https://raw.githubusercontent.com/CosmosContracts/mainnet/main/$CHAIN_ID" && \
3
export PEERS="$(curl -s "$CHAIN_REPO/persistent_peers.txt")"
Copied!
NB: If you are unsure about this, you can ask in discord for the current peers and explicitly set them in ~/.juno/config/config.toml instead.
Setting up the Node
These instructions will direct you on how to initialize your node, synchronize to the network and upgrade your node to a validator. 
Initialize the chain
1
junod init $MONIKER_NAME --chain-id $CHAIN_ID
Copied!
This will generate the following files in ~/.juno/config/
genesis.json 
node_key.json 
priv_validator_key.json
Download the genesis file
1
curl https://raw.githubusercontent.com/CosmosContracts/mainnet/main/$CHAIN_ID/genesis.json > ~/.juno/config/genesis.json
Copied!
This will replace the genesis file created using junod init command with the mainnet genesis.json. 
Set persistent peers
Using the peers variable we set earlier, we can set the persistent_peers in ~/.juno/config/config.toml: 
1
sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$PEERS\"/" ~/.juno/config/config.toml
Copied!
Create (or restore) a local key pair
Either create a new key pair, or restore an existing wallet for your validator:
1
# Create new keypair
2
junod keys add <key-name>
3
​
4
# Restore existing juno wallet with mnemonic seed phrase.
5
# You will be prompted to enter mnemonic seed.
6
junod keys add <key-name> --recover
7
​
8
# Query the keystore for your public address
9
junod keys show <key-name> -a
Copied!
Replace <key-name> with a key name of your choosing.
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.
Get some Juno tokens
You will require some Juno 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.
If you do not have any Juno tokens for you validator you can purchase tokens on Osmosis or Emeris.
Setup cosmovisor
Follow these instructions to setup cosmovisor and start the node.
Using cosmovisor is completely optional. If you choose not to use cosmovisor, you will need to be sure to attend network upgrades to ensure your validator does not have downtime and get jailed.
Syncing the node
After starting the junod 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:
1
# Query via the RPC (default port: 26657)
2
curl http://localhost:26657/status | jq .result.sync_info.catching_up
Copied!
If this command returns true then your node is still catching up. If it returns false then your node has caught up to the network current block and you are safe to proceed to upgrade to a validator node.
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:
1
junod tx staking create-validator \
2
  --amount 9000000ujuno \
3
  --commission-max-change-rate "0.1" \
4
  --commission-max-rate "0.20" \
5
  --commission-rate "0.1" \
6
  --min-self-delegation "1" \
7
  --details "validators write bios too" \
8
  --pubkey=$(junod tendermint show-validator) \
9
  --moniker $MONIKER_NAME \
10
  --chain-id $CHAIN_ID \
11
  --gas-prices 0.025ujuno \
12
  --from <key-name>
Copied!
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:
1
junod tx staking create-validator --help
Copied!
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 ~/.juno/config/:
priv_validator_key.json
node_key.json
It is recommended that you encrypt the backup of these files.