> For the complete documentation index, see [llms.txt](https://docs.onyx.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onyx.org/onyxcoin/utility-and-governance.md).

# Utility & Governance

### XCN Utility and Governance

#### 🔧 Utility & Gas

* **Gas token**: Used to pay for all transactions and smart contract executions across the Onyx L3 blockchain. A portion of every transaction fee is burned, making XCN total supply deflationary.
* **Service payments & discounts**: Required to access and pay for Onyx Cloud (RPC/API) and Sequence ledger services, with XCN holders receiving discounted or premium access.

#### 🗳️ Governance & Staking

* **Governance token**: XCN holders can stake tokens in the Onyx DAO to propose and vote on protocol changes, emissions, treasury allocations, and more. This ensures protocol security.
* **Staking rewards**: Stakers secure the network and gain governance power, while also earning periodic staking rewards.

#### 💱 Payment Instrument

* **Means of paymen**t: XCN is used within the ecosystem to pay commercial fees and access premium features.


---

# 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.onyx.org/onyxcoin/utility-and-governance.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.