> 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/fee-model.md).

# Fee Model

Describes the proposed routing and distribution of launchpad trading fees, including creator, burn, buyback, and protocol allocations.

GetPaid proposes a routing layer that receives launchpad trading fees and distributes them to defined destinations.

```
Launchpad
    ↓
Trading Fee
    ↓
GetPaid Fee Router
    ↓
Fee Allocation
├── Creator
├── Burn
├── Buyback
└── Protocol
```

### Proposed allocation

| Destination         | Proposed share | Intended treatment                                                      |
| ------------------- | -------------: | ----------------------------------------------------------------------- |
| Creator             |            60% | Route trading-fee proceeds to the creator.                              |
| Burn                |            10% | Purchase $GET and send the purchased tokens to a dead address.          |
| Buyback             |            10% | Purchase $GET and retain the purchased tokens in the protocol treasury. |
| Protocol            |            10% | Direct funds toward protocol-controlled uses.                           |
| **Total specified** |        **90%** | **Current routed-fee allocation**                                       |
| **Unspecified**     |        **10%** | **To be finalized before implementation**                               |

{% hint style="warning" %}
The initial fee model currently accounts for 90% of routed fees. The remaining allocation will be finalized before implementation.
{% endhint %}

### Allocation roles

#### Creator

The primary creator allocation is intended to route trading-fee proceeds to the configured creator recipient.

#### Burn

The proposed burn allocation would purchase $GET and send the purchased tokens to a dead address. This is a proposed token mechanism, not a guarantee of supply or price effects.

#### Buyback

The proposed buyback allocation would purchase $GET and retain the purchased tokens in the protocol treasury. These holdings are distinct from protocol funds allocated for operating purposes.

#### Protocol

The proposed protocol allocation is intended to support operations, infrastructure, monitoring, insurance, development, security, and ecosystem grants. Final parameters will be established before implementation.

### Distribution, revenue, and treasury

These terms describe different stages of the proposed economic model.

| Term                | Meaning                                                                                              |
| ------------------- | ---------------------------------------------------------------------------------------------------- |
| Fee distribution    | The split of each routed trading fee among its destinations.                                         |
| Protocol revenue    | The proposed 10% protocol allocation captured from routed fees.                                      |
| Treasury allocation | The protocol-controlled resources intended to support protocol activities and the broader ecosystem. |

GetPaid is pre-testnet. The fee model is proposed and is not deployed, audited, or live.


---

# 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/fee-model.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.