> For the complete documentation index, see [llms.txt](https://whitepaper.usegpu.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.usegpu.app/token-economics/creator-fee.md). # Creator Fee Understand how the pump.fun creator fee is generated, routed, and incorporated into the USE-GPU economic system. Every buy and sell on pump.fun\ → 0.30% creator fee\ → USE-GPU treasury ### Fee source pump.fun charges a 1% platform fee and a separate 0.30% creator fee. The platform fee goes to pump.fun. The creator fee goes automatically to the USE-GPU treasury The fee is handled by pump.fun. USEGPU does not add an on-chain transfer tax or transfer hook. USE-GPU allocates the resulting treasury balance within its economic system ### Economic role The creator fee is the primary revenue source during Phase 1. Its amount depends on trading activity and is not guaranteed Creator fee revenue provides the initial economic input for: * Mining rewards * GPU treasury * Holder sharing * Buyback and burn * Operations GPU rental and inference services are planned future revenue sources. They are not current Phase 1 revenue sources See [Fee Allocation](/token-economics/fee-allocation.md) for the treasury split --- # 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://whitepaper.usegpu.app/token-economics/creator-fee.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.