# Tokenomics **Token Supply**: There is a fixed maximum supply of 1,000,000,000 BYTE. This provides sufficient initial circulation for distribution while maintaining scarcity dynamics long-term through incentive pools and sinks. **Token Allocation**: 10% of the total supply is allocated to the founding team and advisors with a 24 month vesting schedule to incentivize long term commitment. The remainder is distributed through initial exchange offerings, community mining programs, developer grants, and user growth initiatives. **Tokenomics**: A 5% tax is levied on all BYTE transactions which funds ongoing development of Core Systems, Distribution Channels, and collective system enrichment. As revenue materializes through commercial integration, residual income post running costs will fund token buyback and burn initiatives (re: [Decentralized Advertising](https://byteai.gitbook.io/byteai-whitepaper/decentralized-advertising-roadmap-iii)). Reiterating on the discussion in roadmap III, this is a very scalable value creation given the size of the global total addressable market. \**Previously, we had TAO subnet mining as one of our intended revenue streams. We will continue to develop it in the background as a means of funding the operational costs of ByteAI, with surplus utilised in the same way as Ad Revenue.*\ \ *The new roadmaps are visions of a much greater future which we are very much empowered to achieve.* --- # 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://byteai.gitbook.io/byteai-whitepaper/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.