> 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/rake-ecosystem/rakevault.md).

# RakeVault

The RAKE vault that receives harvested fees before the 70/15/15 distribution.

## Fee destination and distribution

RakeVault is the destination for creator-side fees within RAKE. It receives fees after harvest, then applies the defined distribution and buy-burn flow.

```
Token launch
    ↓
Fee recipient = RakeVault
    ↓
Fees accumulate
    ↓
Harvest
    ↓
Fees enter RakeVault
    ↓
Fee distribution / buy-burn
```

At launch, the creator does not receive the fee directly. The fee recipient is configured as RakeVault.

### Harvest and RakeVault

Harvest is the mechanism that moves accumulated fees into RakeVault. It pulls fees from the curve, hook, and escrow.

RakeVault is the destination. Harvest is the transfer mechanism. The fee split is the distribution mechanism applied after the fees enter the vault.

```
Fee sources
    ↓
RakeVault
    ↓
70% creator
15% $RAKE market-buy + burn
15% $PONS market-buy + burn
```

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

### Documented controls

RakeVault has no owner-drain function. An admin cannot directly pull funds from the vault.

The admin also cannot instantly change the swap router. A router change requires a proposal and a two-day wait before acceptance.

Slippage protection enforces a 95% minimum output. The expected price is oracle-derived.

{% hint style="info" %}
If an admin wallet leaks, the attacker cannot directly drain RakeVault. A router change still follows the documented proposal and two-day acceptance process.
{% endhint %}

These controls define specific limits on fund access and router changes. They do not provide an absolute security guarantee.


---

# 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/rake-ecosystem/rakevault.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.