> For the complete documentation index, see [llms.txt](https://pwt-ai.gitbook.io/pwt.ai-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pwt-ai.gitbook.io/pwt.ai-docs/7.-pwt-token-economics.md). # 7. PWT Token Economics #### 77｜What is the total supply of PWT? The total supply of PWT is: 1,000,000,000 PWT #### 78｜How is PWT allocated? * Smart Storage Node Pool: 45% * Content Minting Incentive Pool: 35% * Market Operations: 5% * Initial Liquidity: 4% * Institutional Investment & Ecosystem Advisors: 4% * Developer & Ecosystem Development: 4% * Core Team: 3% #### 79｜Why do the Node Pool and Content Pool have the highest allocation? Smart storage nodes and content assets are the two core production factors of PWT.AI. Together, they account for 80% of the total supply, supporting the long-term growth of network resources and content supply. #### 80｜What services can PWT be used for? PWT can be used in scenarios including smart storage, content minting, AI training, inference, data processing, API services, attention distribution, and ecosystem governance. #### 81｜Is PWT only an incentive token? No. PWT simultaneously serves multiple value functions, including service usage, node participation, ecosystem incentives, staking lock-up, and governance. #### 82｜What are the nine value growth logics of PWT? 1. Extremely low circulation, creating long-term scarcity; 2. Continuous consumption driven by real business; 3. A core token integrating the entire ecosystem; 4. AI applications driving value growth; 5. Node staking reducing circulating supply; 6. Protocol revenue-driven deflation mechanism; 7. Continuous expansion of the developer ecosystem; 8. Ongoing release of enterprise-level demand; 9. Continuous expansion of liquidity through major exchanges. 83｜What is continuous business consumption?\ \ Smart storage, AI training, model inference, API services, and data services will create ongoing PWT usage demand, connecting the token with real business scale. #### 84｜What is node staking lock-up? When participating in storage, computing, and ecosystem expansion, nodes need to hold or stake PWT according to ecosystem rules, reducing short-term circulation and strengthening long-term participation. #### 85｜What is the protocol revenue deflation mechanism? A portion of protocol revenue can be used for PWT buybacks and burns according to ecosystem rules, allowing real business revenue to further influence token supply. #### 86｜Why can the developer ecosystem increase PWT demand? As more APIs, AI Agents, models, and applications join the ecosystem, service usage and token application scenarios will expand simultaneously. #### 87｜How do enterprise demands support PWT value? Enterprise knowledge bases, data services, model calls, and API services can create scalable and sustainable B2B service demand. #### 88｜Do the nine value growth logics mean the price will definitely increase? No. These logics explain PWT’s business utility, circulation mechanism, and ecosystem support. The token price is still influenced by factors such as market conditions, business growth, and liquidity. --- # 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://pwt-ai.gitbook.io/pwt.ai-docs/7.-pwt-token-economics.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.