> 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/no-rug-vector.md).

# No Rug Vector

The source-defined design constraints that prevent owner-drain behavior.

## Direct vault access and router changes

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

This restriction addresses direct fund extraction. It is distinct from the risk of delayed configuration changes.

### Router-change process

An admin cannot change the swap router instantly. A change follows the documented sequence:

```
Router change proposed
    ↓
2-day waiting period
    ↓
Accept
    ↓
New router takes effect
```

The waiting period creates a response window if an administrative credential is compromised. The source does not describe the timelock implementation.

### Execution constraints

| Constraint     | Documented behavior           |
| -------------- | ----------------------------- |
| Minimum output | 95% minimum output protection |
| Expected price | Oracle-derived                |

The 95% value is the documented minimum-output protection. It does not define maximum total loss under every circumstance.

### Admin-wallet leak scenario

If an admin wallet leaks, the attacker still cannot directly drain RakeVault. The attacker could potentially change the router after the documented proposal and two-day process.

{% hint style="info" %}
The delay provides time for the team to respond. It does not make an administrative compromise harmless.
{% endhint %}

The documented model separates two paths:

1. Direct vault draining is restricted by the lack of an owner-drain function.
2. Router configuration remains a delayed administrative risk.


---

# 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/no-rug-vector.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.