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

# Security

RAKE's owner-drain constraints, router-change delay, slippage protection, and execution controls.

## Security model

RAKE implements specific constraints intended to reduce documented failure and abuse paths. These controls address separate layers of the system. They do not create absolute safety guarantees.

| Layer              | Control focus                                  |
| ------------------ | ---------------------------------------------- |
| Vault controls     | Fee custody and administrative access          |
| Protocol controls  | Configuration changes and execution parameters |
| Execution controls | User authorization for money movement          |

### Control architecture

```
User command
    ↓
Parser + schema
    ↓
Echo confirmation
    ↓
Execution
```

The parser and schema are the execution source of truth. The LLM supports the conversation. It cannot bypass money-moving controls.

```
Fees
    ↓
RakeVault
    ↓
Defined distribution
    ↓
Burn / creator allocation
```

RakeVault receives fees for the documented distribution. The source defines a 70/15/15 split and onchain burn verification.

### Documented constraints

* RakeVault has no owner-drain function.
* Router changes require a proposal, two-day wait, and acceptance.
* Slippage protection uses a 95% minimum output.
* Expected price is oracle-derived.
* Echo requires an exact confirmation before money-moving execution.

The following pages examine each control boundary. Start with the direct-vault and delayed-configuration distinction.

{% content-ref url="/spaces/eNzYUwCoXW1vRxzxdeJM/pages/PnOeA1NgJhkbDZdCqgs9" %}
[No Rug Vector](/rake/security/no-rug-vector.md)
{% endcontent-ref %}

{% content-ref url="/spaces/eNzYUwCoXW1vRxzxdeJM/pages/KbggWI8xEbegG0tlSNoQ" %}
[Smart Contract Controls](/rake/security/smart-contract-controls.md)
{% endcontent-ref %}

{% content-ref url="/spaces/eNzYUwCoXW1vRxzxdeJM/pages/rk6qFk2HnYm9VySHldfL" %}
[Execution Safety](/rake/security/execution-safety.md)
{% endcontent-ref %}


---

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