# Tokenomics iDemi will have DEMI as its native token. Token use case - this token will be the basic utility token in the company, some of the fees will be paid in the DEMI token. DEMI token will also give governance and decisive measure to the holders. DEMI token will be deployed on; * BSC. Contract - * Polygon - *coming soon* There will be a maximum DEMI token supply of 90,000,000 This token has various features; * Burnable - yes, the token will have a scheduled burn event * Minting - no, no more than maximum supply will be introduced * Auditing - yes, DEMI will be audited by Certik (The best token auditing company) **Token Distribution** Team tokens will be locked for 5 years and be vested yearly. There will be a scheduled monthly burning event of up to 1% of the total supply. | | Tokens | Percentage(%) | | -------------------------- | -------------- | ------------- | | Liquidity | 13,500,000 | 15 | | Token Security & Insurance | 6,300,000 | 7 | | Team | 9,000,000 | 10 | | Farming and Pools | 13,500,000 | 15 | | Project Development | 22,500,000 | 25 | | Partnership | 9,000,000 | 10 | | Gaming | 11,700,000 | 13 | | Other Exchanges Total | 4,500,000 | 5 | | **Total** | **90,000,000** | **100** | We focus on developing fast and good dApps for every user to profit. 2% of maximum tokens will be introduced to the circulating supply every year. There is guaranteed management of the DEMI market cap and token price fluctuations through dApps launch, buyback, and burning events. As always HOLDER is a WINNER. --- # Agent Instructions: 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: ``` GET https://idemitransfer.gitbook.io/idemi-docs/tokenomics.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.