Skip to main content
This section covers everything needed to operate on the Injective network: setting up nodes, managing upgrades, running the bridge orchestrator, and configuring indexer services.

Architecture

Node types, network topology, consensus layer, and process management

Node Operation

Set up your keyring, configure validators, interact with nodes, and manage Cosmovisor

Join A Network

Install the binary, sync with mainnet or testnet via snapshots, state sync, or block sync

Upgrades

Chain upgrade procedures, Coordinated Upgrades troubleshooting, and the Operator Portal

Architecture

Injective uses CometBFT (formerly Tendermint) consensus with a Byzantine Fault Tolerant (BFT) mechanism, achieving sub-second finality. The network requires bare metal servers with enterprise-grade specifications (128GB RAM, high-clock-speed CPUs, NVMe storage) to handle high-throughput trading activity.

Node types

Key components

Chain upgrades

Injective periodically undergoes coordinated software upgrades at predetermined block heights. All nodes must switch to the new binary to maintain consensus. See Upgrades for procedures and the Coordinated Upgrades guide for troubleshooting.
Last modified on September 2, 2026