# Revenue Allocation

We created a Revenue Allocation framework that we believe will allow the ALF Treasury to not only thrive in the near term, but to continue to grow and expand into the future.

### Revenue Allocation Model

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

Additionally, ALL royalties will flow directly to the ALF Treasury, benefiting all holders. <br>

### 80% of the value created will directly benefit ALF Holders

You read that right!

* 50% of the Revenue will be retained and re-invested back into the Treasury, benefiting all holders proportionally.
* 30% of all Revenue will go directly back to holders through [Reward Airdrops](/utility/holder-rewards.md).

### **The other 20%**

The Team’s goal has been to create a remuneration structure that ties their interests directly to those of the NFT holders. To this end, the only inflows to the Team will come from our collective success.&#x20;

#### **Operational Costs**

10% of revenue earned will be used by The Team to maintain ALF, including:

* ALF Management Team (The Team) Compensation
* Alpha Gatherer Services
* Moderators
* Community Managers
* Hosting (website, bots, etc)
* Any other Team directed activities

#### **Compensation**

10% of the revenue earned will be used to compensate the ALF investment team.&#x20;

This means that their remuneration is not only directly correlated to profit, but the team will not be paid unless a profit is made.

{% hint style="info" %}
The ability to offer any Holder distributions requires the team to create value post-mint. While it is our full intention to offer consistent and meaningful distributions, distributions are NOT guaranteed.
{% endhint %}


---

# 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://whitepaper.aeplife.io/utility/revenue-allocation.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.