# Chain ID

Learn about the Evmos chain-id format

# Official Chain IDs

NOTE: The latest Chain ID (i.e highest Version Number) is the latest version of the software and mainnet.

# Mainnet

Name Chain ID Identifier EIP155 Number Version Number
Evmos 2 evmos_9001-2 evmos 9001 2
Evmos 1 evmos_9001-1 evmos 9001 1

# Testnet

Name Chain ID Identifier EIP155 Number Version Number
Evmos Public Testnet evmos_9000-4 evmos 9000 4
Evmos Public Testnet evmos_9000-3 evmos 9000 3
Olympus Mons Incentivized Testnet evmos_9000-2 evmos 9000 2
Arsia Mons Testnet evmos_9000-1 evmos 9000 1

You can also lookup the EIP155 (opens new window) Chain ID by referring to chainlist.org (opens new window).

chainlist.org website

# The Chain Identifier

Every chain must have a unique identifier or chain-id. Tendermint requires each application to define its own chain-id in the genesis.json fields (opens new window). However, in order to comply with both EIP155 and Cosmos standard for chain upgrades, Evmos-compatible chains must implement a special structure for their chain identifiers.

# Structure

The Evmos Chain ID contains 3 main components

  • Identifier: Unstructured string that defines the name of the application.
  • EIP155 Number: Immutable EIP155 (opens new window) CHAIN_ID that defines the replay attack protection number.
  • Version Number: Is the version number (always positive) that the chain is currently running. This number MUST be incremented every time the chain is upgraded or forked in order to avoid network or consensus errors.

# Format

The format for specifying and Evmos compatible chain-id in genesis is the following:

Copy {identifier}_{EIP155}-{version}

The following table provides an example where the second row corresponds to an upgrade from the first one:

ChainID Identifier EIP155 Number Version Number
evmos_9000-1 evmos 9000 1
evmos_9000-2 evmos 9000 2
... ... ... ...
evmos_9000-N evmos 9000 N