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

# Fee Routing

Defines the proposed FeeRouter flow, configurable fee destinations, default allocation, and distinction between fee distribution, protocol revenue, and treasury allocation.

GetPaid proposes a routing path between a launchpad's trading fee and its final destinations.

```
Launchpad → Trading Fee → FeeRouter → Configurable Allocation → Final Destinations
```

The proposed FeeRouter would receive an intercepted fee, apply a configured split, and route each portion independently. This separates fee distribution from the launchpad's trading interface.

### Proposed default split

| Destination | Allocation |
| ----------- | ---------: |
| Creator     |        60% |
| Burn        |        10% |
| Buyback     |        10% |
| Protocol    |        10% |

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

### Final destinations

* **Creator routing:** sends the creator portion to the configured fee recipient.
* **Burn allocation:** purchases $GET, then sends it to the dead address.
* **Buyback allocation:** purchases $GET, then holds it in treasury.
* **Protocol allocation:** moves funds to the protocol treasury.

The split is configurable in the proposed architecture.

### Distribution, revenue, and treasury

These terms describe separate parts of the proposed model:

| Term                | Meaning                                                                   |
| ------------------- | ------------------------------------------------------------------------- |
| Fee distribution    | The division of each routed trading fee among destinations.               |
| Protocol revenue    | The proposed 10% protocol cut from fees routed through GetPaid.           |
| Treasury allocation | Funds directed to the protocol treasury through that protocol allocation. |

Protocol funds are intended to support operations, insurance, development, security, and ecosystem grants. This describes intended use, not current revenue or active treasury operations.

{% hint style="info" %}
GetPaid is pre-testnet. No fee routing is deployed, audited, or live.
{% endhint %}


---

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