# Token Allocation **Presale** 90% of the tokens are distributed in the presale:\ \ 40% Tokens for Presale\ 36% Tokens for Liquidity\ 2% DxSale Fee\ 12% DxSale buffer for 2.9v, which are then burned automatically Read up here regarding the 2+12%\ \ \ **Production Wallet** 5% of the tokens are set aside as a production wallet and locked over 2 year. This wallet will vest in increments of 10. As the token grows the costs for marketing, audits and website building etc. will eat up the initial project budget. We have set aside this wallet to ensure that we can support the project throughout it's first 2 years. Beyond this, we expect GameChangers to have revenue streams from the industry through requested community votes.\ \ **Dev Wallets** A total of 5 dev wallets holding 1% each have been allocated for the team.\ \ Each dev wallet will be locked over 1 year, vesting in increments of 5. It's important for a project to have developers who has a stake in the project. Any project that lacks a dev wallet is a scam in our view. The developers is then instead taking funds out of the "marketing" wallet or having taxes go towards a "dev wallet". In our opinion these are just hidden fees made to trick you. We are open about our stake in this project, but are also assuring the holders by locking the tokens up for the first year.\ \ **Safu**\ \ This approach assures that all wallets have locked tokens, that are only released in small portions. Along with the locked LP from the DxSale there is no way for anyone to rug or impact the price in any capacity. Since the contract will be generated well before the Presale (minimum 1 week) you can take a look at all DxLocks to assure yourself of the fact. We are 100% transparent with this.\ \ Contract Address: 0x10b2d426f987b618e9e130044c648df8bbefdf94 --- # 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://gamechangersbsc.gitbook.io/gamechangers/token/token-allocation.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.