> 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/smart-contract-controls.md).

# Smart Contract Controls

The delayed router-change process and contract-level constraints defined for RAKE.

## Smart contract controls

The following controls describe documented behavior for RAKE's fee routing and execution constraints. They do not describe an audit, upgradeability model, or ownership structure beyond these controls.

| Control                 | Documented behavior            | Purpose                                    |
| ----------------------- | ------------------------------ | ------------------------------------------ |
| RakeVault routing       | Fees enter RakeVault           | Centralizes fee processing                 |
| Owner-drain restriction | No owner-drain function        | Prevents direct vault extraction           |
| Router delay            | Proposal + 2-day wait + accept | Creates a response window                  |
| Slippage protection     | 95% minimum output             | Limits execution below the defined minimum |
| Expected price          | Oracle-derived                 | Provides the expected execution reference  |
| Fee split               | 70/15/15                       | Defines fee allocation                     |
| Burn address            | Dead address                   | Makes burns verifiable onchain             |

### Fee routing and allocation

RakeVault receives the documented fee flow. The source states the 70/15/15 fee split cannot be changed.

```
Fees
    ↓
RakeVault
    ↓
70 / 15 / 15 distribution
```

The dead address for burn verification is:

```
0x000000000000000000000000000000000000dEaD
```

Sending the documented burn allocation to this address makes the burn verifiable onchain.

### Administrative constraints

The owner cannot drain RakeVault. A swap-router change must be proposed, wait two days, then be accepted.

The expected execution price is oracle-derived. Slippage protection requires a 95% minimum output. The source does not specify the oracle source or contract implementation.


---

# 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/smart-contract-controls.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.