Skip to main content

Join Injective Mainnet

Hardware Specification

Validators should expect to provision one or more data center locations with redundant power, networking, firewalls, HSMs and servers.

We initially recommend this minimum hardware specifications and they might rise as network usage increases.

4+ vCPU x64 2.0+ GHz
32+ GB RAM

Install injectived and peggo

sudo mv peggo /usr/bin
sudo mv injectived /usr/bin

Initialize a new Injective Chain node

Before actually running the Injective Chain node, we need to initialize the chain, and most importantly its genesis file.

# The argument <moniker> is the custom username of your node, it should be human-readable.
export MONIKER=<moniker>
# the Injective Chain has a chain-id of "injective-1"
injectived init $MONIKER --chain-id injective-1

Running this command will create injectived default configuration files at ~/.injectived.

Prepare configuration to join Mainnet

You should now update the default configuration with the Mainnet's genesis file and application config file, as well as configure your persistent peers with a seed node.

git clone

# copy genesis file to config directory
cp mainnet-config/10001/genesis.json ~/.injectived/config/genesis.json

# copy config file to config directory
cp mainnet-config/10001/app.toml ~/.injectived/config/app.toml

You can also run verify the checksum of the genesis checksum - 573b89727e42b41d43156cd6605c0c8ad4a1ce16d9aad1e1604b02864015d528

sha256sum ~/.injectived/config/genesis.json

Then open update the persistent_peers field present in ~/.injectived/config/config.toml with the contents of mainnet-config/10001/seeds.txt and update the timeout_commit to 800ms.

cat mainnet-config/10001/seeds.txt
nano ~/.injectived/config/config.toml

Configure systemd service for injectived

Edit the config at /etc/systemd/system/injectived.service:


ExecStart=/bin/bash -c '/usr/bin/injectived --log-level=error start'


Starting and restarting the systemd service

sudo systemctl daemon-reload
sudo systemctl restart injectived
sudo systemctl status injectived

# enable start on system boot
sudo systemctl enable injectived

# To check Logs
journalctl -u injectived -f

Sync with the network

Option 1. State-Sync

You can use state-sync to join the network by following the below instructions.

sudo systemctl stop injectived
sudo injectived tendermint unsafe-reset-all --home ~/.injectived
CUR_HEIGHT=$(curl -sS | jq .result.block.header.height | tr -d '"')
TRUSTED_HASH=$(curl -sS$TRUST_HEIGHT | jq .result.block_id.hash)
perl -i -pe 's|enable = false|enable = true|g' ~/.injectived/config/config.toml
perl -i -pe 's|rpc_servers = ".*?"|rpc_servers = "'$RPC_SERVERS'"|g' ~/.injectived/config/config.toml
perl -i -pe 's/^trust_height = \d+/trust_height = '$TRUST_HEIGHT'/' ~/.injectived/config/config.toml
perl -i -pe 's/^trust_hash = ".*?"/trust_hash = '$TRUSTED_HASH'/' ~/.injectived/config/config.toml
sudo systemctl start injectived

Option 2. Snapshots

You can find snapshots on:

  1. ChainLayer.
  2. Polkachu.
  3. HighStakes.
  4. AutoStake.

Alternatively you can use the archival or pruned snapshots on AWS.


aws s3 sync --acl public-read --delete --no-sign-request s3://injective-snapshots/mainnet/injectived/daily/data $HOME/.injectived/data
aws s3 sync --acl public-read --delete --no-sign-request s3://injective-snapshots/testnet/injectived/daily/wasm $HOME/.injectived/wasm


aws s3 sync --acl public-read --delete --no-sign-request s3://injective-snapshots/mainnet/injectived/pruned/data $HOME/.injectived/data
aws s3 sync --acl public-read --delete --no-sign-request s3://injective-snapshots/testnet/injectived/pruned/wasm $HOME/.injectived/wasm


For any further questions, you can always connect with the Injective Team via Discord, Telegram, and email.

Discord Telegram [E-mail](mailto: