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

# Revenue Share

####

<figure><img src="/files/MmbIwMfs5WIOvxTQo8i0" alt=""><figcaption></figcaption></figure>

#### Fees

The protocol generates revenue from each harvest. 10% of each harvest is taken and sent to the processor with each harvest. 3% of harvest is reimbursed to the harvest caller to cover gas fees, 3% is sent to the team, and 4% is sent to the revenue share.

#### Revenue Share

Users can deposit IMPLS into the single sided staking revenue share contract and they will earn a share of the protocol revenue. The protocol revenue is in PLS, offering participants a way to stake their IMPLS and earn WPLS. The Revenue share is located on the [stake page here](https://impls.finance/stake).


---

# 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://impls.gitbook.io/impls/protocol/revenue-share.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.