# Revenues of Medusa

From start, our focus has been on creating a cryptocurrency that could be powered by revenues. Like stocks in a public traded business.

The Medusa Ecosystem will feature several revenue streams based on its utilities. 

In MDUSA Token, we will take a 3% fee of the transactions as revenue for the company. 

We kept the token with a low fee, because our main source of revenues will not come from the transactions of the MDUSA token.

{% hint style="info" %}
You can see the [tokenomics](https://medusa-protocol.gitbook.io/whitepaper/medusa-token/tokenomics) again if you skipped this part.
{% endhint %}

Our main source of revenues as a business comes from the projects under the Medusa scope. 

Every project within our ecosystem will have a small percentage transaction fee flowing directly into MDUSA token, as buybacks and burns. 

In the case of OceanCats for example, a share of the total revenues from NFT sales, merchandising and networking contracts, is distributed with holders of the MDUSA token.

Funds raised from different projects will be used to sustain and keep on growing the ecosystem.

Medusa Easy-Staking Protocol (MESP), Medusa Token Launcher and other DeFi Services (which we will provide in the future) have the earnings coming directly to the whole Medusa Company to be allocated in the most efficient manner.

<figure><img src="https://2593809925-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FozMKBjA1KpXftZeS3ma4%2Fuploads%2FuwquFTXHwOZG48BP7Y4g%2Frevenues.jpg?alt=media&#x26;token=6c36e247-b5c5-46a9-80b3-e83043505a8c" alt=""><figcaption></figcaption></figure>


---

# 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://medusa-protocol.gitbook.io/whitepaper/revenues/revenues-of-medusa.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.