Run a local Injective chain to configure genesis, test native execution module behavior, or query native state over the CLI, gRPC, or REST. Use the published injectived release binary for the version you want to test. For Solidity and EVM precompiles, use the bootstrapped EVM localnet.
Initialize the Chain
Install injectived and install jq. Use a fresh directory for the local chain. The following commands use Bash or Zsh.
init creates the node’s keys and configuration under $LOCAL_CHAIN_HOME/config. Pass the same --home to each command that reads or changes the local node’s files.
Use inj for staking, governance deposits, the crisis fee, and minting.
Fund the Validator Account
Create a validator operator account in the local test keyring. An INJ amount in a native CLI command is an integer in the smallest unit, followed by inj. One INJ is 1000000000000000000inj.
Add the Validator to Genesis
Create and collect a genesis transaction (gentx). It registers the operator, self-delegates the specified stake, and registers the local consensus public key.
Start and Query the Node
Set minimum-gas-prices in $LOCAL_CHAIN_HOME/config/app.toml. For local development, you can use minimum-gas-prices = "0inj". The same file configures the application’s gRPC and REST services. Use config.toml for CometBFT settings such as the RPC listener and consensus timeouts.
From another terminal, check the chain ID and verify that the block height increases:
Expect injective-1000. To query bank balances or other module state, use injectived query with --node tcp://localhost:26657. See Interact with Nodes for CLI, gRPC, Go, and REST examples. Last modified on November 19, 2026