# Yeet Revenue Sharing

YeetDAO's most remarkable aspect will be its robust and sustainable economy, meticulously designed to create a thriving circular ecosystem. Our primary objective revolves around fostering value for every holder. By seamlessly integrating innovative utilities, investors and creators will both reap the benefits of Yeet's cutting-edge tools and products. With a strong focus on sustainability and inclusivity, we envision a community-driven platform where every member can contribute and prosper.\
\
Our project will feature a revenue sharing model, designed to give back to the community through indirect means. A portion of the revenue generated is dedicated to acquiring bluechip NFTs, which are then raffled off holders using tickets purchased with $YEET tokens. This innovative approach enables us to invest in valuable assets while offering our vibrant community exciting chances to win prestigious NFTs. Together, we create a cycle of support and appreciation, building a thriving ecosystem where everyone benefits.\
\
Get ready for an exciting twist in our revenue sharing model! This gamified approach will incentivize holders to retain their Yeet NFTs unlisted, and it's a groundbreaking idea unique to our project. Unlike anything seen before, this significant upgrade promises to elevate previous models. Stay tuned for the reveal—we'll disclose all the details at a later date.


---

# 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://yeet-4.gitbook.io/yeet-whitepaper/detailed-information/yeet-revenue-sharing.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.
