> 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/tokenomics/usdrake.md).

# $RAKE

The source-defined mechanics and role of the $RAKE token within RAKE.

$RAKE is the RAKE token. It launches on Pons V2 with ETH as its pair.

Its source-defined protocol connection is the harvest-linked buy-and-burn allocation. This connection does not establish supply, allocation, vesting, governance, staking, or price mechanics.

### Role in the fee flow

Every applicable harvest routes fees into RakeVault. The vault uses 15% of the fees it receives to market-buy $RAKE and burn the purchased amount.

```
Harvest
    ↓
RakeVault
    ↓
15% allocation
    ↓
Market-buy $RAKE
    ↓
Burn
    ↓
0x000000000000000000000000000000000000dEaD
    ↓
Onchain verification
```

The burn is an outcome of protocol fee activity. It is not described as a discretionary action advertised separately from harvest.

### Verification

The purchased $RAKE is sent to the dead address:

```
0x000000000000000000000000000000000000dEaD
```

Transfers to this address can be verified onchain. The source does not specify a fixed amount burned per harvest, a burn schedule, or a supply-reduction forecast.

### Scope

The $RAKE market-buy allocation is one part of RakeVault's fixed 70/15/15 distribution. The other allocations route 70% to the creator wallet and 15% to a $PONS market buy and burn.

See [Fee Distribution](/rake/tokenomics/fee-distribution.md) for the complete routing mechanism.


---

# 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/tokenomics/usdrake.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.