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

# About

## Overview

The Chain Network is the blockchain infrastructure powering the Zentachain ecosystem. It provides a decentralized network committed to delivering secure, reliable, and cost-effective infrastructure for the Telecom and IoT sector.

CHAIN is an ERC-20 token on Ethereum with a fixed supply of 5,000,000 tokens. It serves as the native utility token for staking, governance, service payments, and node rewards across the ecosystem.

## Chain Developer

Developers who want to build on the Chain Network or join the ecosystem can find all necessary documentation at the developer hub.

{% embed url="<https://devs-chain.zentachain.io/docs/intro>" %}

## Chain Ecosystem

Discover the products and services built by the Zentachain team — including Zentalk, Zentamesh, Zentanode, and more.

{% embed url="<https://zentachain.io/ecosystem>" %}

## Join Chain Network

Whether you're an experienced developer or just starting, the Chain Network welcomes contributors from all backgrounds. By actively participating, you become part of building the future of decentralized communication and infrastructure.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zentachain.io/chain-network/about.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.