> For the complete documentation index, see [llms.txt](https://atom3-1.gitbook.io/atom3-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atom3-1.gitbook.io/atom3-whitepaper/tokenomics/usdaom-utinities.md).

# $AOM Utinities

Tokenomics Structure: The tokenomics of $AOM are carefully designed to ensure sustainability and encourage active participation. The structure incorporates elements such as staking, participatory governance, and rewards.

* Staking: Users have the opportunity to stake their $AOM tokens, contributing to the security and stability of the platform. By staking their tokens, users can earn rewards and actively participate in the governance of Atom3.
* Participatory Governance: Atom3 embraces a community-driven governance model, giving token holders the ability to influence the platform's direction and evolution. Through voting and engagement, token holders can actively participate in decision-making processes, shaping the future of Atom3.
* Rewards: Atom3 rewards users who contribute to the ecosystem's growth and development. This can include activities such as providing valuable feedback, contributing to the community, or developing innovative solutions on the platform. By incentivizing active participation, Atom3 aims to foster a vibrant and engaged community.


---

# 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://atom3-1.gitbook.io/atom3-whitepaper/tokenomics/usdaom-utinities.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.