> 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.md).

# How RAKE Works

The launch, harvest, fee distribution, and Echo confirmation mechanics used by RAKE.

## How RAKE operates

RAKE connects a token lifecycle with controlled execution for money-moving actions. These flows serve different purposes, but operate as one protocol system.

The lifecycle flow determines where launch fees go. The execution flow determines when an action can move money.

### Protocol lifecycle

```
Token launch
    ↓
Fees accumulate
    ↓
Permissionless harvest
    ↓
RakeVault
    ↓
70/15/15 distribution
    ↓
$RAKE and $PONS buy-burn
```

A token launches on Pons V2 with RakeVault set as its fee recipient. Fees accumulate across the launch system until harvest moves them into RakeVault.

RakeVault then applies the fixed allocation. The creator receives its share. The remaining allocations market-buy and burn $RAKE and $PONS.

### Transaction execution

```
Money-moving command
    ↓
Echo draft
    ↓
Exact confirmation
    ↓
Execute

or

Mismatch / timeout
    ↓
Cancel
```

Money-moving commands follow a separate execution path. RAKE creates a draft containing the intended action and amount. Execution requires an exact `confirm` reply before the draft expires.

### Four connected mechanics

| Mechanic          | Role in the system                                                    |
| ----------------- | --------------------------------------------------------------------- |
| Launch            | Deploys a token on Pons V2 and configures RakeVault as fee recipient. |
| Harvest           | Lets any actor move accumulated fees into RakeVault.                  |
| Fee Split         | Applies the fixed 70/15/15 distribution to fees entering RakeVault.   |
| Echo Confirmation | Requires exact user confirmation before money-moving actions execute. |

The first three mechanics describe the route from launch to distribution. Echo Confirmation governs a separate class of user actions, including actions that transfer, trade, or otherwise move assets.

Start with [Launch](/rake/how-rake-works/launch.md) to follow a token into the RAKE lifecycle.


---

# 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.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.