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

# Xai Basic Concepts

### Xai Summary

Xai operates as an Arbitrum Orbit chain, harnessing Anytrust technology to achieve maximum speed and minimal costs. Unlike most Orbit chains that are "self-managed," Xai benefits from direct technical support courtesy of Offchain Labs. This support is not available to other orbit chains and is a crucial component of Xai as a strategic gaming initiative within the Arbitrum ecosystem.

The strategy and growth of Xai's ecosystem are overseen by the Xai Foundation, and Offchain Labs provides technical assistance under the guidance of the Xai Foundation. In a departure from other Orbit chains, Xai boasts a canonical bridge within the Arbitrum ecosystem. Additionally, Xai incorporates unique enhancements, including elevated gas and contract limits, which foster a more favorable environment for ambitious blockchain game development and gameplay. Finally, Xai has its own custom gas fee token, self-named “$XAI”.

***

### Nitro

All Arbitrum chains are built on top of Arbitrum Nitro, which is the foundational technology underneath all chains in the ecosystem.  Nitro runs a fork of [Geth](https://docs.arbitrum.foundation/dao-glossary#geth) and uses WebAssembly as its underlying VM for fraud proofs.  You can read about Nitro in detail [here](https://github.com/OffchainLabs/nitro/blob/master/docs/Nitro-whitepaper.pdf).

***

### Anytrust

An Arbitrum protocol that manages data availability with a permissioned set of parties known as the[ Data Availability Committee (DAC)](https://docs.arbitrum.foundation/dao-glossary#data-availability-committee-dac). This protocol reduces transaction fees by introducing an additional trust assumption for data availability in lieu of Ethereum's[ Trustless](https://docs.arbitrum.foundation/dao-glossary#trustless) data availability mechanism.&#x20;

***

### Arbitrum Layer2s

[Arbitrum Nova](https://docs.arbitrum.foundation/dao-glossary#arbitrum-nova) is an example of an AnyTrust chain;[ Arbitrum One](https://docs.arbitrum.foundation/dao-glossary#arbitrum-one) is an alternative chain that implements the purely trustless (and more L1-gas intensive)[ Arbitrum Rollup Protocol](https://docs.arbitrum.foundation/dao-glossary#arbitrum-rollup-protocol). Both chains are built on top of Nitro.

***

### Orbit Chains

Arbitrum Orbit lets 3rd parties create their own self-managed Arbitrum Rollup and AnyTrust chains. Arbitrum offers Rollup and AnyTrust technology for maximum flexibility in building Orbit chains. As with all chains in the Arbitrum ecosystem, both Arbitrum Rollups and Arbitrum Anytrust Orbit chains are built with Nitro as the underlying technology.

***


---

# 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://xai-foundation.gitbook.io/xai-network/about-xai/xai-protocol/xai-basic-concepts.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.
