> For the complete documentation index, see [llms.txt](https://docs.rakelaunch.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rakelaunch.xyz/rake/how-rake-works/fee-split.md).

# Fee Split

The 70/15/15 RAKE creator-side distribution and its separation from Pons V2's protocol side.

## RakeVault distribution

Fees entering RakeVault follow a fixed 70/15/15 distribution. The split applies to the creator-side fees that enter RakeVault. It does not apply to the full Pons V2 trade fee.

| Allocation | Share | Action                      |
| ---------- | ----: | --------------------------- |
| Creator    |   70% | Sent to creator wallet      |
| $RAKE      |   15% | Market-buy $RAKE, then burn |
| $PONS      |   15% | Market-buy $PONS, then burn |

```
Fees entering RakeVault
    ↓
70% → Creator wallet
15% → Market-buy $RAKE → Burn
15% → Market-buy $PONS → Burn
```

### Fixed allocation

**Creator: 70%**\
RakeVault sends 70% of the fees it receives to the creator wallet.

**$RAKE: 15%**\
RakeVault uses 15% to market-buy $RAKE and burn it.

**$PONS: 15%**\
RakeVault uses 15% to market-buy $PONS and burn it.

The split cannot be changed. The owner cannot drain the vault. Burns are verifiable onchain at:

```
0x000000000000000000000000000000000000dEaD
```

### Pons V2 fee boundary

Pons V2 charges a 1% fee per trade. That fee has two sides:

```
Pons V2 trade fee: 1%

70% → creator side → RakeVault → RAKE 70/15/15 process
30% → Pons protocol
```

Only the 70% creator side enters RakeVault. RAKE applies its 70/15/15 process only after those fees enter RakeVault.

The remaining 30% goes to the Pons protocol. RAKE does not touch that allocation.


---

# 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://docs.rakelaunch.xyz/rake/how-rake-works/fee-split.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.