Join a Network - Injective Docs

Set up and sync an Injective node on Mainnet, Testnet, or a local development network.

Mainnet
Testnet
Local Network

Injective Mainnet has a chain-id of injective-1.

Sync Options

Snapshot restore, state sync, and block sync

Node Software

Install injectived, configure, and run

Hardware

Minimum and recommended specifications

Sync Options

Choose how to bootstrap your node with chain data. For most operators, snapshot restore is the fastest path to a running node.Option 1. Snapshot Restore (recommended)Download a pre-built snapshot and extract it into your data directory. This is the fastest and most reliable way to sync a new node.Injective provides official pruned snapshots (goleveldb, ~2-3 GB) and the community maintains additional options. See the Snapshots page on the Chain Portal for download links, usage instructions, and community providers.

Validators: You must back up and restore priv_validator_state.json during snapshot recovery. See the Validator Troubleshooting Guide for the full procedure.

# Example: download and extract
sudo systemctl stop injectived
rm -rf ~/.injectived/data
wget -O snapshot.lz4 <SNAPSHOT_URL>
lz4 -d snapshot.lz4 | tar xf - -C ~/.injectived/
sudo systemctl start injectived

Option 2. State Sync (CometBFT P2P)State sync bootstraps a node by downloading a state machine snapshot from peers via the CometBFT P2P layer, rather than replaying all historical blocks. It requires two trusted RPC servers. See the RPC Providers page on the Chain Portal for available endpoints. Configure it in config.toml under [statesync]:

[statesync]
enable = true
rpc_servers = "<rpc_server_1>,<rpc_server_2>"
trust_height = <recent_height>
trust_hash = "<block_hash_at_trust_height>"
trust_period = "168h0m0s"

To obtain the trust height and hash:

# Get a recent height and its hash from a trusted RPC
LATEST=$(curl -s https://sentry.tm.injective.network/block | jq -r '.result.block.header.height')
TRUST_HEIGHT=$((LATEST - 2000))
TRUST_HASH=$(curl -s "https://sentry.tm.injective.network/block?height=$TRUST_HEIGHT" | jq -r '.result.block_id.hash')
echo "trust_height = $TRUST_HEIGHT"
echo "trust_hash = \"$TRUST_HASH\""

State sync does not restore the wasm/ directory. CometBFT state sync restores the IAVL state tree but not the CosmWasm compiled contract bytecode stored in ~/.injectived/data/wasm/. Without these files, the node will produce an AppHash mismatch immediately after sync completes.If you encounter this, either:

Switch to snapshot restore (Option 1). Injective’s official snapshots include the wasm/ directory
Obtain the wasm/ directory from a trusted source and place it at ~/.injectived/data/wasm/ before starting the node

PebbleDB users: Injective’s official snapshots use goleveldb only. PebbleDB snapshots are not maintained. If you run PebbleDB and cannot use a snapshot restore, you must source the wasm/ directory separately when using state sync.

Option 3. Block Sync (full replay)The default behavior. The node downloads and replays every block from peers. Slowest method but requires no external snapshots. Not practical for mainnet unless syncing from a recent snapshot height.Sync method comparison:

Method	Speed	Includes wasm?	Notes
Snapshot Restore	Fast (minutes)	Yes (official snapshots)	Recommended for most operators
State Sync	Fast (minutes)	No - causes AppHash mismatch without manual wasm restore	Configured in `config.toml` `[statesync]`
Block Sync	Slow (days)	N/A (builds from execution)	Default, not practical for mainnet from genesis

Peer discovery

Your node needs peers to sync with the network. Add seeds or persistent peers to the [p2p] section of ~/.injectived/config/config.toml. Community providers maintain up-to-date seed and peer lists:

Polkachu Injective Seeds
Decentrio Injective Infrastructure (seeds, peers, address book)

You can also download a pre-built address book for faster peer discovery:

# Decentrio address book
wget -O ~/.injectived/config/addrbook.json \
  https://backend.decentrio.ventures/snapshots/injective/addrbook.json

Node Software

Install `injectived`

Each Injective core release includes injectived, peggo (the Peggy bridge orchestrator), and libwasmvm in a single zip. Validators must run peggo alongside their node. Non-validator node operators only need injectived.

# Download the latest release
wget https://github.com/InjectiveFoundation/injective-core/releases/latest/download/linux-amd64.zip
unzip linux-amd64.zip
sudo mv injectived /usr/bin
sudo mv libwasmvm.x86_64.so /usr/lib

# Validators also need peggo
sudo mv peggo /usr/bin

Initialize a New Injective Node

Before running an Injective node, initialize the chain and genesis file:

# The argument <moniker> is the custom username of your node. It should be human-readable.
export MONIKER=<moniker>
injectived init $MONIKER --chain-id injective-1

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

Prepare Configuration to Join Mainnet

Download the mainnet genesis file. Injective provides this alongside the official snapshots:

# Download the mainnet genesis file
wget -O ~/.injectived/config/genesis.json \
  http://injective-mainnet-snapshots.s3-website.gra.io.cloud.ovh.net/genesis.json

Verify the checksum:

sha256sum ~/.injectived/config/genesis.json
# Expected: 573b89727e42b41d43156cd6605c0c8ad4a1ce16d9aad1e1604b02864015d528

Configure seeds for peer discovery (see Peer discovery in the Sync Options section) and set timeout_commit to 300ms in ~/.injectived/config/config.toml.

Configuring the node using `app.toml` and `config.toml`

Two configuration files are automatically generated inside ~/.injectived/config:

config.toml: configures the consensus layer (CometBFT). Learn more in the consensus layer documentation.
app.toml: configures the application and execution layer of the node, including state pruning strategies, telemetry, gRPC and REST server configurations, state sync, and more.

Configure `systemd` service for `injectived` (optional)

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

[Unit]
  Description=injectived

[Service]
  WorkingDirectory=/usr/bin
  ExecStart=/bin/bash -c '/usr/bin/injectived --log-level=error start'
  Type=simple
  Restart=always
  RestartSec=5
  User=root

[Install]
  WantedBy=multi-user.target

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

The service should be stopped before and started after snapshot data has been loaded into the correct directory.

# to stop the node
sudo systemctl stop injectived

# to start the node
sudo systemctl start injectived

Hardware

Node operators should deploy bare metal servers to achieve optimal performance. Validator nodes must meet the recommended hardware specifications, particularly the CPU requirements, to ensure high uptime.

Minimum	Recommendation
RAM Memory 128GB	RAM Memory 128GB
CPU 12 cores	CPU 16 cores
CPU base clock 3.7GHz	CPU base clock 4.2GHz
Storage 2TB NVMe	Storage 2TB NVMe
Network 1Gbps+	Network 1Gbps+

SupportFor any further questions, you can always connect with the Injective Team via Discord, Telegram, or email

Hardware Specification

Node operators should deploy bare metal servers to achieve optimal performance. Additionally, validator nodes must meet the recommended hardware specifications and particularly the CPU requirements, to ensure high uptime.

Minimum	Recommendation
RAM Memory 128GB	RAM Memory 128GB
CPU 12 cores	CPU 16 cores
CPU base clock 3.7GHz	CPU base clock 4.2GHz
Storage 2TB NVMe	Storage 2TB NVMe
Network 1Gbps+	Network 1Gbps+

Install `injectived` and `peggo`

See the Injective releases repo for the most recent releases. Non-validator node operators do not need to install peggo.

wget https://github.com/InjectiveLabs/testnet/releases/latest/download/linux-amd64.zip
unzip linux-amd64.zip
sudo mv peggo /usr/bin
sudo mv injectived /usr/bin
sudo mv libwasmvm.x86_64.so /usr/lib 

Initialize a New Injective Chain Node

Before running Injective node, we need to initialize the chain as well as the node’s genesis file:

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

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

Prepare Configuration to Join Testnet

You should now update the default configuration with the Testnet’s genesis file and application config file, as well as configure your persistent peers with seed nodes.

git clone https://github.com/InjectiveLabs/testnet.git

# copy genesis file to config directory
aws s3 cp --no-sign-request s3://injective-snapshots/testnet/genesis.json .
mv genesis.json ~/.injectived/config/

# copy config file to config directory
cp testnet/corfu/70001/app.toml  ~/.injectived/config/app.toml
cp testnet/corfu/70001/config.toml ~/.injectived/config/config.toml

You can also run verify the checksum of the genesis checksum - a4abe4e1f5511d4c2f821c1c05ecb44b493eec185c0eec13b1dcd03d36e1a779

sha256sum ~/.injectived/config/genesis.json

Configure `systemd` Service for `injectived`

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

[Unit]
  Description=injectived

[Service]
  WorkingDirectory=/usr/bin
  ExecStart=/bin/bash -c '/usr/bin/injectived --log-level=error start'
  Type=simple
  Restart=always
  RestartSec=5
  User=root

[Install]
  WantedBy=multi-user.target

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

Refer to the Polkachu Injective Testnet Node Snapshot to download a snapshot and sync with the network.SupportFor any further questions, you can always connect with the Injective Team via Discord, Telegram, or email.

To easily set up a local node, download and run the setup.sh script from the injective-core repository. Use the script version that matches your installed injectived version.

# Replace the version tag with the one matching your injectived binary
# For example, to use the script for v1.18.3:
wget https://raw.githubusercontent.com/InjectiveFoundation/injective-core/v1.18.3/setup.sh
chmod +x ./setup.sh # Make the script executable
./setup.sh

The setup.sh script in the legacy injective-chain-releases repository is outdated and only compatible with injectived v1.14.1 and earlier. Always use the script from the InjectiveFoundation/injective-core repository that corresponds to your chain version.

Start the node by running:

injectived start # Blocks should start coming in after running this

For further explanation on what the script is doing and more fine-grained control over the setup process, continue reading below.

Initialize the Chain

Before running Injective node, we need to initialize the chain as well as the node’s genesis file:

# The <moniker> argument is the custom username of your node. It should be human-readable.
injectived init <moniker> --chain-id=injective-1

The command above creates all the configuration files needed for your node to run as well as a default genesis file, which defines the initial state of the network. All these configuration files are in ~/.injectived by default, but you can overwrite the location of this folder by passing the --home flag. Note that if you choose to use a different directory other than ~/.injectived, you must specify the location with the --home flag each time an injectived command is run. If you already have a genesis file, you can overwrite it with the --overwrite or -o flag.The ~/.injectived folder has the following structure:

.                                   # ~/.injectived
  |- data                           # Contains the databases used by the node.
  |- config/
      |- app.toml                   # Application-related configuration file.
      |- config.toml                # Tendermint-related configuration file.
      |- genesis.json               # The genesis file.
      |- node_key.json              # Private key to use for node authentication in the p2p protocol.
      |- priv_validator_key.json    # Private key to use as a validator in the consensus protocol.

Modify the `genesis.json` File

At this point, a modification is required in the genesis.json file:

Change the staking bond_denom, crisis denom, gov denom, and mint denom values to "inj", since that is the native token of Injective.

This can easily be done by running the following commands:

cat $HOME/.injectived/config/genesis.json | jq '.app_state["staking"]["params"]["bond_denom"]="inj"' > $HOME/.injectived/config/tmp_genesis.json && mv $HOME/.injectived/config/tmp_genesis.json $HOME/.injectived/config/genesis.json
cat $HOME/.injectived/config/genesis.json | jq '.app_state["crisis"]["constant_fee"]["denom"]="inj"' > $HOME/.injectived/config/tmp_genesis.json && mv $HOME/.injectived/config/tmp_genesis.json $HOME/.injectived/config/genesis.json
cat $HOME/.injectived/config/genesis.json | jq '.app_state["gov"]["deposit_params"]["min_deposit"][0]["denom"]="inj"' > $HOME/.injectived/config/tmp_genesis.json && mv $HOME/.injectived/config/tmp_genesis.json $HOME/.injectived/config/genesis.json
cat $HOME/.injectived/config/genesis.json | jq '.app_state["mint"]["params"]["mint_denom"]="inj"' > $HOME/.injectived/config/tmp_genesis.json && mv $HOME/.injectived/config/tmp_genesis.json $HOME/.injectived/config/genesis.json

The commands above will only work if the default .injectived directory is used. For a specific directory, either modify the commands above or manually edit the genesis.json file to reflect the changes.

Create Keys for the Validator Account

Before starting the chain, you need to populate the state with at least one account. To do so, first create a new account in the keyring named my_validator under the test keyring backend (feel free to choose another name and another backend):

injectived keys add my_validator --keyring-backend=test

# Put the generated address in a variable for later use.
MY_VALIDATOR_ADDRESS=$(injectived keys show my_validator -a --keyring-backend=test)

Now that you have created a local account, go ahead and grant it some inj tokens in your chain’s genesis file. Doing so will also make sure your chain is aware of this account’s existence from the genesis of the chain:

injectived add-genesis-account $MY_VALIDATOR_ADDRESS 100000000000000000000000000inj --chain-id=injective-1

$MY_VALIDATOR_ADDRESS is the variable that holds the address of the my_validator key in the keyring. Tokens in Injective have the {amount}{denom} format: amount is an 18-digit-precision decimal number, and denom is the unique token identifier with its denomination key (e.g. inj). Here, we are granting inj tokens, as inj is the token identifier used for staking in injectived.

Add the Validator to the Chain

Now that your account has some tokens, you need to add a validator to your chain. Validators are special full-nodes that participate in the consensus process in order to add new blocks to the chain. Any account can declare its intention to become a validator operator, but only those with sufficient delegation get to enter the active set. For this guide, you will add your local node (created via the init command above) as a validator of your chain. Validators can be declared before a chain is first started via a special transaction included in the genesis file called a gentx:

# Create a gentx.
injectived genesis gentx my_validator 1000000000000000000000inj --chain-id=injective-1 --keyring-backend=test

# Add the gentx to the genesis file.
injectived genesis collect-gentxs

A gentx does three things:

Registers the validator account you created as a validator operator account (i.e. the account that controls the validator).
Self-delegates the provided amount of staking tokens.
Link the operator account with a Tendermint node pubkey that will be used for signing blocks. If no --pubkey flag is provided, it defaults to the local node pubkey created via the injectived init command above.

For more information on gentx, use the following command:

injectived genesis gentx --help

Configuring the Node Using `app.toml` and `config.toml`

Two configuration files are automatically generated inside ~/.injectived/config:

config.toml: used to configure Tendermint (learn more on Tendermint’s documentation), and
app.toml: generated by the Cosmos SDK (which Injective is built on), and used for configurations such as state pruning strategies, telemetry, gRPC and REST server configurations, state sync, and more.

Both files are heavily commented. Refer to them directly to tweak your node.One example config to tweak is the minimum-gas-prices field inside app.toml, which defines the minimum gas prices the validator node is willing to accept for processing a transaction. If it’s empty, make sure to edit the field with some value, for example 10inj, or else the node will halt on startup. For this tutorial, let’s set the minimum gas price to 0:

 # The minimum gas prices a validator is willing to accept for processing a
 # transaction. A transaction's fees must meet the minimum of any denomination
 # specified in this config (e.g. 0.25token1;0.0001token2).
 minimum-gas-prices = "0inj"

Run a Localnet

Now that everything is set up, you can finally start your node:

injectived start # Blocks should start coming in after running this

This command allows you to run a single node, which is is enough to interact with the chain through the node, but you may wish to run multiple nodes at the same time to see how consensus occurs between them.

Sync Options

Node Software

Hardware

​Sync Options

​Peer discovery

​Node Software

​Install injectived

​Initialize a New Injective Node

​Prepare Configuration to Join Mainnet

​Configuring the node using app.toml and config.toml

​Configure systemd service for injectived (optional)

​Hardware

​Hardware Specification

​Install injectived and peggo

​Initialize a New Injective Chain Node

​Prepare Configuration to Join Testnet

​Configure systemd Service for injectived

​Sync with the network

​Initialize the Chain

​Modify the genesis.json File

​Create Keys for the Validator Account

​Add the Validator to the Chain

​Configuring the Node Using app.toml and config.toml

​Run a Localnet

Sync Options

Peer discovery

Node Software

Install `injectived`

Initialize a New Injective Node

Prepare Configuration to Join Mainnet

Configuring the node using `app.toml` and `config.toml`

Configure `systemd` service for `injectived` (optional)

Hardware

Hardware Specification

Install `injectived` and `peggo`

Initialize a New Injective Chain Node

Prepare Configuration to Join Testnet

Configure `systemd` Service for `injectived`

Sync with the network

Initialize the Chain

Modify the `genesis.json` File

Create Keys for the Validator Account

Add the Validator to the Chain

Configuring the Node Using `app.toml` and `config.toml`

Run a Localnet