> For the complete documentation index, see [llms.txt](https://ivex.gitbook.io/ivex-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ivex.gitbook.io/ivex-1/4.-ivex-token-usdivex/4.2-utility.md).

# 4.2 Utility

### Key utilities of IVEX token

1. Staking. IVEX is simply an ecosystem of infrastructure and tools, so it does not provide any native computing resources and would rely on users to stake tokens to execute transactions and/or otherwise maintain integrity of the IVES network. By transferring IVEX tokens to staking, users can participate in the operation of the ecosystem, for which they may receive rewards in the form of new IVEX tokens.
2. $IVEX serves as an exclusive payment instrument within the ecosystem (TBA). For example, it is planned that on the ecosystem's private island in Greece, $IVEX will be the only native currency accepted. $IVEX can be used as the medium of exchange to purchase cars, yachts, and even real estate on the island.
3. Similarly, $IVEX is utilised as a payment instrument in the metaverse (TBA), so it may be utilised to purchase various supported NFT assets in the metaverse (these NFTs may grant certain utilities or represent various rights such as shares in real businesses). For example, a user may spend $IVEX to purchase an NFT plot in the metaverse and become a co-owner of that plot in the real physical world. Only by owning a certain number of $IVEX tokens can the user get the right to purchase such NFTs.
4. $IVEX holders may participate in project governance through voting and decision-making within the ecosystem (TBA). For instance, if a project involves a football club, users can vote on the design of the uniforms or the schedule of friendly matches.


---

# 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://ivex.gitbook.io/ivex-1/4.-ivex-token-usdivex/4.2-utility.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.