> ## Documentation Index
> Fetch the complete documentation index at: https://docs.injective.network/llms.txt
> Use this file to discover all available pages before exploring further.

# Network Architecture

> How Injective validators, sentries, relayers, light clients, and API services work together.

Injective nodes run `injectived`, the Injective Core executable. As a node daemon, it runs Injective’s native execution modules and the EVM, and uses CometBFT for peer networking and consensus. The same executable provides command line tools for querying chain state and submitting transactions. See [Install the Mainnet release](https://docs.injective.network/infra/run-node.md#install-the-mainnet-release) for node binaries.

Validators are nodes that help secure Injective by bonding native INJ and proposing and voting on blocks. Their voting power reflects their bonded stake, including INJ delegated to them. CometBFT commits a block once validators representing more than two thirds of voting power precommit to it. This gives committed blocks subsecond finality under normal network conditions. Sentries carry peer traffic for validators, relayers submit cross chain messages, and API services provide access to chain data.

## Consensus and relay paths

This diagram shows a validator behind sentry peers. Operators can use separate full nodes for public queries and transaction submission.

```mermaid theme={null}
flowchart TB
    Public["Public peers"] <-->|"P2P blocks and votes"| Sentry["Sentry full nodes"]
    Sentry <-->|"P2P blocks and votes"| Validator["Validators"]
    Cosmovisor["Cosmovisor"] -.->|"Manages injectived"| Validator
    Cosmovisor -.->|"Manages injectived"| Sentry
    Full["Injective query and broadcast node"] <-->|"P2P sync"| Public
    Light["CometBFT light client"] -->|"Requests signed headers and proofs"| Full
    IBC["IBC relayer"] <-->|"Updates and packets with proofs"| Full
    IBC <-->|"Updates and packets with proofs"| Remote["IBC counterparty"]
    Peggo["Peggo"] <-->|"Claims and confirmations"| Full
    Peggo <-->|"Events and batches"| Ethereum["Ethereum Peggy contract"]

    classDef node fill:#E8F4FF,stroke:#0082FA,color:#082B4A
    classDef service fill:#EFF5FB,stroke:#53799D,color:#082B4A
    class Sentry,Validator,Full node
    class Cosmovisor,Light,IBC,Peggo service
```

### Validators, sentries, and light clients

* **Validators** are bonded consensus participants. They run `injectived`, validate blocks, and use validator keys to sign proposals and votes. See [Validator Setup](https://docs.injective.network/infra/validator-mainnet.md).
* **Sentries** are full nodes that peer with a validator and the wider network so the validator can keep its peer address and RPC private. They verify blocks and relay peer traffic. A full node can prune historical state and still validate new blocks. An archival node keeps historical state for queries and backfill. See [Run a Mainnet Node](https://docs.injective.network/infra/run-node.md), [Hardware Requirements](https://docs.injective.network/infra/hardware.md), and [Archival Setup](https://docs.injective.network/infra/archival-setup.md).
* **CometBFT light clients** verify signed headers from a trusted starting point and use verified headers to check application state proofs. They can query a full node without executing every transaction or storing the complete chain state. IBC uses this verification through its `07-tendermint` light client. A counterparty chain uses that client to verify Injective headers and check proofs for packets and acknowledgements. See [CometBFT](https://github.com/cometbft/cometbft) and [IBC Go](https://github.com/cosmos/ibc-go).
* **Cosmovisor** is an optional process manager that automatically polls `$DAEMON_HOME/data/upgrade-info.json` for an upgrade signal. At the scheduled height, `injectived` writes the upgrade plan to that file. Cosmovisor then switches to the prepared binary and restarts the node if `DAEMON_RESTART_AFTER_UPGRADE` is enabled, as it is by default. See [Cosmovisor setup](https://docs.injective.network/infra/cosmovisor.md) and [Cosmovisor v1.5.0](https://github.com/cosmos/cosmos-sdk/tree/tools/cosmovisor/v1.5.0/tools/cosmovisor).

### IBC relayers and Peggo

* **IBC relayers** watch both chains, pay gas, and submit client updates, packet proofs, acknowledgements, and timeouts. Each receiving chain uses its onchain IBC light client of the counterparty to verify the proofs. See [Hermes](https://github.com/informalsystems/hermes), [IBC Go](https://github.com/cosmos/ibc-go), and the [IBC precompile reference](https://docs.injective.network/developers-evm/ibc-precompile.md).
* **Peggo** is the separate orchestrator for the Peggy bridge between Injective and Ethereum. It observes Ethereum bridge events, submits claims and confirmations to Injective, and relays validator set updates and withdrawal batches to the Ethereum contract. See [Peggo setup](https://docs.injective.network/infra/validator-mainnet/peggo.md), the [Peggy module](https://docs.injective.network/developers-native/injective/peggy.md), and [Peggo releases](https://github.com/InjectiveFoundation/injective-core/releases).

## How applications read the chain

Use native query endpoints for current chain state, the indexer for indexed market and transaction history, and the EVM Gateway for Ethereum JSON-RPC. Each service can use its own upstream full node.

```mermaid theme={null}
flowchart TB
    Node["injectived full node<br/>CometBFT RPC · native gRPC · EVM gRPC"]
    Node -->|"Native queries and event streams"| Native["Native SDKs and services"]
    Node -->|"Blocks and chain events"| Indexer["Injective Indexer"]
    Node -->|"CometBFT blocks and EVM gRPC queries"| Gateway["EVM Gateway"]
    Indexer -->|"Market, trade, and account data"| Trading["Trading apps and explorers"]
    Gateway -->|"Ethereum JSON-RPC over HTTP and WebSocket"| EVM["Wallets and EVM apps"]

    classDef node fill:#E8F4FF,stroke:#0082FA,color:#082B4A
    classDef service fill:#EFF5FB,stroke:#53799D,color:#082B4A
    class Node node
    class Indexer,Gateway service
```

* **Built-in EVM gRPC** is the `injective.evm.v1.Query` service inside `injectived`. It provides EVM state queries and simulation methods such as `EthCall` and `EstimateGas` to gRPC clients, including EVM Gateway. See the [EVM query definitions](https://github.com/InjectiveLabs/injective-proto/blob/master/all_protos/injective/evm/v1/query.proto).
* **EVM Gateway** runs separately from `injectived`. It reads CometBFT block data and uses native gRPC queries, builds a local index of EVM blocks, transactions, receipts, and logs, and serves Ethereum JSON-RPC. See the [EVM Gateway explainer](https://docs.injective.network/developers-evm/evm-gateway.md) and [Gateway source](https://github.com/InjectiveLabs/evm-gateway).
* **Injective Indexer** processes chain events into queryable records for markets, orders, fills, and account activity. See [Query Indexer](https://docs.injective.network/developers-native/query-indexer.md), [Indexer API architecture](https://docs.injective.network/developers/concepts/indexer-api.md), and the [Indexer repository](https://github.com/InjectiveLabs/injective-indexer), which requires repository access.

> [!WARNING]
>
> Use Injective Core’s optional built-in Ethereum JSON-RPC server for local development and testing only. [EVM Gateway](https://docs.injective.network/developers-evm/evm-gateway.md) is the recommended Ethereum JSON-RPC server for production.

For service addresses, see [Mainnet Public Endpoints](https://docs.injective.network/infra/public-endpoints.md) and [Testnet Public Endpoints](https://docs.injective.network/testnet/public-endpoints.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.