# Revenue Share

### Revenue Sharing for holders

Token holding amounts will determine the revenue share and from which avenue they will be distributed from. There will be multiple sources of income in the ecosystem from ADS to product & template purchases in-house.

### Tiers & Benefits

Each tier will have one of 2, or all sets of benefits attached to it; rev share & product perks and freebies. Specifics are outlined below;

| TIERS  | Token Holdings (%) | Rev Distro $                                                                                  | Product perks                                                            |
| ------ | ------------------ | --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| Tier 1 | 1.5                | <ul><li>ADS Rev (50%)</li><li>UI, Site & CA (80%)</li><li>Staking multiplier (1.5x)</li></ul> | Free lifetime access to all products & first access to new Beta releases |
| Tier 2 | 1                  | <ul><li>ADS Rev (50%)</li><li>UI, Site & CA (80%)</li></ul>                                   | Limited amount of free deployments & templates p/m                       |
| Tier 3 | 0.8                | <ul><li>UI, Site & CA (80%)</li></ul>                                                         | 20% Discounts on all products                                            |
| Tier 4 | 0.5                | <ul><li>UI, Site (80%)</li></ul>                                                              | 10% Discounts on all products                                            |


---

# 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://dapp-ai-1.gitbook.io/dapp-ai-product-docs/revenue-share.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.