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

# Overview

![(Fig. 2 Orbit Chain Structure)](/files/-LvnyWnFWLOf1MI3WWbD)

**Orbit Chain ( Hub chain )**

* All Public blockchains will be connected to Orbit Chain through the IBC zone to share information, data and asset using a standard format. Orbit Chain will work as the hub chain to gather all the information, data and assets from all different public blockchains. Dapps can easily utilize with smart contracts for their utility.
* Orbit Chain will also support simultaneous communication for multiple public blockchains.

**Orbit Inter Blockchain Communication zone ( IBC zone )**

* Orbit Chain and Public Chain will communicate through a decentralized Inter-Blockchain Communication (IBC) Zone. The IBC Zone will verify information and data from each public blockchain. Those verifications will be processed on the blockchain so it is safer, more reliable and will operate with decentralized communication which doesn’t require centralized operating and validating process.


---

# 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.orbitchain.io/orbit-chain-network/overview.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.