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

# Two Tokens, One Ecosystem

XYO Layer One uses a dual-token model to create a powerful, scalable blockchain ecosystem optimized for DePIN, data, and AI applications. This structure separates the foundational and transactional layers of the network, ensuring long-term sustainability without compromising speed or usability. The two tokens—$XYO and $XL1—each serve a distinct purpose that contributes to the health and growth of the network.

$XYO is a deflationary token with a fixed supply. It is designed for [staking](/xyo-layer-one/staking.md) and securing the network, offering long-term value alignment and stability. Token holders who stake $XYO contribute to the structural integrity of the blockchain, reinforcing trust and decentralization across the ecosystem.

$XL1, by contrast, is the utility token that powers day-to-day activity on XYO Layer One. It is described as inflationary, but this inflation is deliberately restrained. The inflation rate approaches 0.7% per year. $XL1 is used for gas [fees](/xyo-layer-one/architecture/transaction-fees.md), smart contract execution, real-time rewards, and other core functions of the blockchain. XL1 is effectively deflationary through active use. This design ensures that XYO Layer One maintains an economic balance, even while supporting high-throughput applications.


---

# 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.xyo.network/about-xyo/xyo-101/xyo-layer-one/off-chain-data-producers.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.