> For the complete documentation index, see [llms.txt](https://whitepaper.getpaid.family/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.getpaid.family/fee-economics/revenue.md).

# Revenue

Explains the proposed protocol-revenue mechanism, where a protocol allocation from routed trading fees supports future protocol operations.

GetPaid proposes protocol revenue through a 10% protocol allocation from fees routed through the Fee Router.

```
Trading Volume
    ↓
Trading Fees
    ↓
GetPaid
    ↓
Protocol Allocation
    ↓
Protocol Revenue
```

This model depends on adoption and routed activity. With 0 token integrations, the proposed model produces 0 revenue.

### Proposed mechanism

For a routed fee amount of $$F$$, the proposed protocol allocation is:

$$
\text{Protocol allocation} = F \times 10%
$$

For example, a $100 routed fee would produce a $10 protocol allocation under the proposed split.

{% hint style="warning" %}
The overall fee allocation currently accounts for 90% of routed fees. The complete allocation remains subject to final specification before implementation.
{% endhint %}

### Intended uses

Protocol revenue is intended to support the resources required to operate and develop the protocol:

* Operations, including gas, infrastructure, and monitoring.
* Insurance for potential fraud, bugs, or exploits.
* Development, audits, security work, and ecosystem grants.

### Revenue is adoption-dependent

The protocol allocation is an economic mechanism, not established revenue. No current revenue, recurring revenue, profit, margin, or financial projection is stated.

GetPaid is pre-testnet and has no deployed or audited fee-routing system. Revenue can arise only if integrations route fees through the protocol after implementation.


---

# 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://whitepaper.getpaid.family/fee-economics/revenue.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.