> For the complete documentation index, see [llms.txt](https://eon-rift.gitbook.io/eon-rift-litepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eon-rift.gitbook.io/eon-rift-litepaper/tokenomics.md). # Tokenomics ### *Under Construction* We plan to launch our own coin for the EON RIFT ecosystem of digital & physical collectibles, comics, games and merchandise. Our coin will be a unique digital asset that not only has exciting in-game utilities but can also be used for real-life benefits. We're currently working with tokenomics experts to map out the best way to implement our coin to ensure long term value for the project, and will release the token when it has real utility across our ecosystem. The current planned utility for the coin spans digital and physical use cases. We will update this section of the litepaper as soon as we have defined a distribution model of the token which supports the long term success of our IP. --- # 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://eon-rift.gitbook.io/eon-rift-litepaper/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.