# Revenue Distribution

### Revenue Distribution

Giving back to the community is in our DNA, and that is the reason the team decided to implement the following: the platform provides projects with the exposure, liquidity, and tools they need for a successful launch while ensuring that $TRP token holders benefit from the ecosystem’s growth.

### How the Launchpad Works

When a project launches on Tripple.fun, they configure:\
✅ Token price per sale\
✅ Token allocation\
✅ Sale duration\
✅ Key project details for investors

### Investors can then participate by purchasing tokens directly through the platform. For example, if an investor contributes $100:

* 95% goes to the project that is launching its token.
* 5% is retained by Tripple.fun as a platform service fee.

### Revenue Distribution Breakdown

Out of the 5% service fee collected per investment, Tripple.fun redistributes earnings as follows:

* 30% is allocated to $TRP token holders as a reward for supporting the platform.
* 50% is reinvested into the platform’s development, covering upgrades, security, and marketing to drive growth.
* 20% is reserved for the core team and operational expenses, ensuring long-term sustainability.

This transparent and structured revenue-sharing model ensures that $TRP holders directly benefit from the platform’s success, creating an economy where early adopters and long-term believers in Tripple.fun earn a consistent share of launchpad activity.

<br>


---

# 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://docs.tripple.fun/platform/revenue.md?ask=<question>
```

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.