> For the complete documentation index, see [llms.txt](https://docs.pumptogether.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pumptogether.xyz/revenue-share.md).
# Revenue Share
Pumptogether's platform protocol generates revenue from 3 primary sources:
* Directly from DEX liquidity LP pool fees in the case of direct deployments to DEXES like [`uniswap`](https://app.uniswap.org/),[ Radium](https://raydium.io/swap/) and [Jupiter](https://jup.ag/). LP pool fees are routed to daily revenue pools and made available for claims by eligible platform users and DAO members
* Pump Launcher Launch Fees : Pumptogether implements a standard 3% fee for all developer launches on the platform. This is in addition to the default pump.fun fees. Launch fees are routed to daily revenue pools and made available for claims by eligible platform users and DAO members proportionally.
* Pump Launcher Trading Fees: Pumptogether also collects a 3% fee on all locking and trading activities associated with Pump Launcher launches. Trading fees are routed to daily revenue pools and made available for claims by eligible platform users and DAO members proportionally.
### Revenue sharing :
1. 60% of all daily platform fees are earned by vePumpTGT NFT holders
2. 25% of all daily platform fees are earned by Project deployers/ traders
3. 10%: Daily XP of all daily platform fees is retained by DAO Treasury
4. 5% of all daily platform fees are earned by project promoters, verified by trading activity of referred traders
All revenue share percentages are subject to change based on DAO voting outcomes
---
# 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://docs.pumptogether.xyz/revenue-share.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.