> For the complete documentation index, see [llms.txt](https://docs.fyuz.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fyuz.fun/how-fyuz-works/security.md).

# 🔒 Security

Fyuz is built so that the rug-pull vectors of typical token launches *cannot exist*, and admin power is deliberately constrained.

## 🛡️ Protocol-level guarantees

* **No presale, no team allocation** — 100% of supply starts on the curve or reserved for graduation LP.
* **Curve funds are always redeemable** — while a token is on the curve, its BNB reserve backs every sell; nothing can withdraw it except trading.
* **LP locked forever** — at graduation the liquidity position is held permanently by the liquidity manager contract. There is no function to withdraw or transfer it out; for V3 the position NFT is retained (not burned) only so fees stay collectable.
* **Leftover tokens burned** at graduation. 🔥

## ⏳ Admin constraints

* **24-hour emergency timelock** — emergency actions can't be executed instantly.
* **Liquidity-manager changes are timelocked** — graduation funds flow through the liquidity manager, so swapping it is deliberately slow and visible.
* **Oracle staleness guard** — the [Chainlink BNB/USD feed](/how-fyuz-works/chainlink-integration.md) is rejected if its data is older than the staleness threshold, preventing graduation decisions on stale prices.
* **Price-impact and liquidity floors** — hard caps on maximum price impact and minimum liquidity protect the curve's integrity in edge cases.

{% hint style="warning" %}
🧐 Fyuz secures the *platform* — it cannot vet the *culture*. Any two icons can be fused and launched by anyone. Check the [analytics tab](/trader-tools/token-analytics.md) (holder concentration, creator holdings) before sizing a position.
{% endhint %}


---

# 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.fyuz.fun/how-fyuz-works/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.