> For the complete documentation index, see [llms.txt](https://knight-dead.gitbook.io/dead-knight-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knight-dead.gitbook.io/dead-knight-whitepaper/ecosystem/economic-model.md). # Economic Model ### **Dual Token** Dead Knight has two types of tokens: Dead Knight Metaverse Token and Dead Knight Token Dead Knight Metaverse token (DKM) is known as the governance token and pre-minted tokens of Dead Knight. The number of limited tokens released in the project can only be used to buy characters. The number of pre-minted tokens released has been decided at the beginning of the project, which means there will not be any situation of issuing more tokens during the whole process that might lead to token inflation. Dead Knight token (DK) is known as in-game tokens that users earn when they win each game and can be used in in-game transactions. Player can use to buy consumable items, booster packs, heal character & other in-game function like upgrade Equipment, special dungeons entry fee and tournament entry fee. ### Economic ![](/files/wbDZbhN6w5bjcDqd4296) --- # 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://knight-dead.gitbook.io/dead-knight-whitepaper/ecosystem/economic-model.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.