> For the complete documentation index, see [llms.txt](https://docs.hellobotnft.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hellobotnft.co/hellobot-universe/mechanism/tokenomics.md).
# Tokenomics
Figure 4: Distribution plan for Hellobot Universe Official NFT collection
* Hellobot Universe NFT collection is on **Ethereum chain**.
* The distribution plan for NFTs is summarized in Figure 4. There is a **total of 5,555 NFTs**, with 555 reserved for the team and 5,000 for community mint. 2,000 NFTs will be reserved for whitelisted people and 3,000 will be available through a public mint. The creator fee will be 7.5%.
* We will put the profits generated from the business models we create, into a smart contract vault. The funds that go into this vault will be used for the scale-out of the project and distribution based on community contributions.
* To quantitatively verify the degree of community contribution, we will implement a point system. Points will be rewarded to the members who actively participate in our NORI and will be used to show us how much contribution each individual has put into our project.
* Details will be added when the system is ready for launch.
---
# 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.hellobotnft.co/hellobot-universe/mechanism/tokenomics.md?ask=&goal=
```
`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.