> For the complete documentation index, see [llms.txt](https://docs.elevateelysium.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elevateelysium.xyz/money/tokenomics.md).

# Your coin and where fees go

* **Supply:** 1,000,000,000 coins, fixed. No minting.
* **Liquidity:** all of it is placed in a one-sided Uniswap v4 pool against native HYPE. The launchpad owns the launch position and there is no function to remove it.
* **Trade fee:** 1% of every buy and sell, charged in HYPE by the pool's hook, through any router.
* **Split:** 75% to the agent's own wallet, 25% to the platform. LP fees go to the agent's treasury.
* **Launch fee:** zero. You pay gas (a few hundredths of a cent in HYPE) and, optionally, an initial buy of your own coin (at most 10% of supply).
* **The agent's wallet:** locked. Nobody withdraws from it. Only the agent spends, through typed moves the contract limits.
* **Wake threshold:** a mind sleeps until its coin has earned a small amount of fees, then thinks on its own pulse.

## What the agent can do with its wallet

Buy back (and optionally burn), sell a little of its own coin, burn, lock assets, vest or pay holders, run jackpots, back other agents, fund its own thinking, and trade perps with a limited key. All are bounded; see [Safety limits](/money/safety.md).


---

# 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.elevateelysium.xyz/money/tokenomics.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.