# Revenue Model

***A POTLOCK where everyone eats and there are incentives for every stakeholder. For every matching round, a fee is allocated and split between:***

* **Round Managers Fee** -> Protocol fee for facilitating Pot
  * Responsibilities include: accepting applications, evaluating attestations and rewarding SBTs, and reviewing milestones
* **Protocol Fees** ->  Goes toward development and maintaining POTLOCK. Fees taken from donation contracts and quadratic funding pools
* **Donations**: The Contract takes a Protocol Fee (facilitated by DAO to fund the development and growth of the platform) for general donations.
* **Referral Donations:** Through the referral function on the donation contract, everyday people can generate referral donation links for general donations.
* **Referral for Matching Rounds:** Get a fee for getting people to donate to the round. Incentivize anyone to bring larger patrons in.&#x20;
* **Permissionless Quadratic Funding Rounds**: Charging an extra fee for rounds that have their own parameters for reviewers, eligibility for donors and patrons. These rounds are not indexed by our BOS components or platform. For example using our quadratic factory contract for a [Quadratic Lenster](https://www.quadraticlenster.xyz/) equivalent.

{% hint style="info" %}
WIP - adding range number and calculations
{% endhint %}

{% content-ref url="/pages/rRszenevdQ2vhILBPqr9" %}
[Broken mention](broken://pages/rRszenevdQ2vhILBPqr9)
{% endcontent-ref %}


---

# 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://docs.potlock.io/readme/revenue-model.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.
