> For the complete documentation index, see [llms.txt](https://docs.quantpad.company/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quantpad.company/quantum-hooks/guarantees-and-risks.md).

# Guarantees and risks

What the Quantum Hooks program guarantees, and the risks it can't remove.

## What you can rely on

* Allocations, split wallets and lock schedules are written before the coin exists. Nobody can edit them afterwards, including you and Quant Pad.
* Pulses, burns and Fusion are permissionless once the keeper's grace period passes, so hooks keep running even if Quant Pad's keeper stops.
* The keeper can post Entanglement epochs and run burns and Fusion, but it has no instruction that sends the well's SOL anywhere else.

## What you should know

* The keeper decides who each Entanglement epoch pays, and epochs are at least 20 hours apart. An epoch's claims open only after a delay set on-chain, 6 hours by default. Until then, Quant Pad can cancel the epoch, which returns its SOL to the holder reserve.
* Meteora can upgrade its programs, and its operators can change a migrated pool's fees or pause it. No Meteora admin can reassign a coin's creator away from its well.
* Creator fees are a share of volume (the trading fee less Meteora's protocol share), so hooks scale with trading activity.
* Buybacks are market orders and can be front-run. Each burn is capped in size to limit that.

{% hint style="danger" %}
The Quantum Hooks program has not been independently audited yet.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.quantpad.company/quantum-hooks/guarantees-and-risks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.