> For the complete documentation index, see [llms.txt](https://etfswap.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://etfswap.gitbook.io/whitepaper/token-details/revenue-sharing.md).

# Revenue Sharing

One of the primary advantages of the ETFS token is the project's pledge to transfer a share of the platform's daily earnings to token holders. There will be two major mechanisms for token holders to share revenue, which are detailed in further detail in the ETF Token part of the whitepaper.

Staked $ETFS - As an incentive for keeping and staking ETF tokens, up to 20% of ETFSwap’s daily earnings will be funneled towards our stakers.

This will be done on a regular basis and will scale based on the number of ETFs each user has staked. 60% of the incentives will be given in ETFs, with the remaining 40% utilized to buy and burn ETFs on the open market, making the ETF token deflationary.

Token holders can opt to become liquidity providers in return for a predetermined rate of interest, allowing them to form a variety of different liquidity pairings. If a holder, for example, creates an ETFs/ETH pair, the fixed rate of interest will be paid in ETH.


---

# 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:

```
GET https://etfswap.gitbook.io/whitepaper/token-details/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.