Joining the SSC Mainnet as a Full Node

Steps to Join as a Full Node Post-Genesis

1. Initialize the sscd instance on this machine by running sscd init <moniker> --chain-id ssc-1. The init command also generates certain configuration files in the home directory for SSC (default ~/.ssc). Example:

sscd init validator --chain-id ssc-1

1. Next, update persistent_peers information in ~/.ssc/config/config.toml using the persistent peers provided by the Saga team. You will update this in the P2P section of config.toml file.

sed -i 's/persistent_peers = ""/persistent_peers = "[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:24956,[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:26656,[email protected]:36656,[email protected]:24956,[email protected]:26656,[email protected]:26656,[email protected]:26656"/g' ~/.ssc/config/config.toml

1. Copy the genesis.json file provided by the Saga team to ~/.ssc/config/, overwriting any existing genesis file in that location.

# fetch the genesis
wget -O genesis.json 'https://raw.githubusercontent.com/sagaxyz/mainnet/main/genesis/genesis.json'

# copy it to your ssc home directory
mv genesis.json ~/.ssc/config

1. Start the SSC node on this machine using sscd start to start the node. Important: You should ideally start the local validator as a systemd service on this machine so it will restart if the machine goes down and is rebooted.

Your full node will sync with the SSC network by replaying all of the transactions and blocks committed so far and will be ready for us one it is fully in sync with the SSC network.