> For the complete documentation index, see [llms.txt](https://docs.flaunch.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flaunch.gg/features/creator-revenue.md).

# Creator Revenue

Swap fees are shared between creators and communities and the split is decided by the creator themselves. The creator can choose to take from 0% up to 100% of the coin's revenue.

{% hint style="info" %}
Revenue split is immutable and cannot be changed after the coin has launched.
{% endhint %}

* For creators, the revenue is streamed on every swap, paid in ETH
* For communities, the revenue is streamed into [auto buybacks](/features/auto-buybacks.md)

The creator can choose to burn the tokens that are automatically bought back, or they can turn off auto buybacks to accumulate ETH that can be spent on market buying the coin.

<figure><img src="/files/DFlGwtWWxeil9njkYGzI" alt="" width="563"><figcaption><p>Devs can choose their own adventure...</p></figcaption></figure>

Revenue streams are fully decentralized and ownership of the “Memestream” is tokenized as an NFT. These NFTs are transferable. You can read about the implications of this in the [Memestream](/features/royalty-nft.md) section.

The right dev, flaunching the right coin, could find themselves with an annual revenue stream in the millions.

If MOTHER had been Flaunched, Iggy would have a multi-million dollar stream of passive income with at least 20% going to coin holders. The same goes for WIF, MOODENG and many, many others. Instead, those revenues were donated to the platform they launched on.

Flaunched coins retain *all* the value for the coin and creator.


---

# 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.flaunch.gg/features/creator-revenue.md?ask=<question>&goal=<endgoal>
```

`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.