> For the complete documentation index, see [llms.txt](https://docs.metanovaverse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metanovaverse.com/technical-concepts/chain-id.md).

# Chain ID

### Official Chain IDs <a href="#official-chain-ids" id="official-chain-ids"></a>

{% hint style="info" %}
The latest Chain ID (i.e highest Version Number) is the latest version of the software and mainnet.
{% endhint %}

<table><thead><tr><th width="165">Name</th><th width="163">Chain ID</th><th>Identifier</th><th width="153">EIP155 Number</th><th>Version Number</th></tr></thead><tbody><tr><td>Metanovaverse</td><td>mnova_10096-1</td><td>mnova</td><td>10096</td><td>1</td></tr></tbody></table>

### The Chain Identifier <a href="#the-chain-identifier" id="the-chain-identifier"></a>

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](https://docs.tendermint.com/master/spec/core/genesis.html#genesis-fields). However, in order to comply with both EIP155 and Cosmos standard for chain upgrades, Metanovaverse-compatible chains must implement a special structure for their chain identifiers.

### Structure <a href="#structure" id="structure"></a>

The Metanovaverse Chain ID contains 3 main components

* **Identifier**: Unstructured string that defines the name of the application.
* **EIP155 Number**: Immutable [EIP155](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-155.md) `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 <a href="#format" id="format"></a>

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

```
{identifier}_{EIP155}-{version}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.metanovaverse.com/technical-concepts/chain-id.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.