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

# How Quantum Hooks work

How a Quant Pad coin's creator fees flow from trades into its well and out through the hooks.

Quantum Hooks work on the one stream every coin has: its creator fees. A Quant Pad coin's Meteora creator is the coin's own **well**, a program-controlled address, and the hooks decide where every lamport goes.

<figure><img src="https://3333211986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWu2Zj9LCnjL5ul1zbj2X%2Fuploads%2Fgit-blob-b8d7a81907e40d5de60886076248006ed9f6cedf%2Fdiagram-fee-flow.jpg?alt=media" alt="Trades pay a trading tax. Meteora keeps its share and the creator fee flows into the coin&#x27;s well. Each pulse splits the well&#x27;s fees four ways: Creator share is paid to the launcher, Quantum Burn buys and burns the coin, Entanglement shares SOL with holders, and Fusion adds locked liquidity. An optional protocol share, capped at 10%, can be taken first."><figcaption></figcaption></figure>

## Key terms

* **Well:** a program-controlled address unique to each Quantum coin. It is the coin's Meteora creator, so creator fees accumulate for it.
* **Pulse:** collects the well's creator fees and splits them by the allocation fixed at launch.
* **Keeper:** Quant Pad's automated service. It runs pulses, burns and Fusion deposits, and posts Entanglement epochs. If the keeper stops, anyone can run pulses, burns and Fusion after a grace period.

## Protocol share

Quantum Hooks can take a protocol share of each fee pulse before it is split. The share is capped at 10% on-chain, and any share is shown before you sign.

## Learn more

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Fee modules</strong></td><td>Where each slice of a pulse goes.</td><td><a href="https://3333211986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWu2Zj9LCnjL5ul1zbj2X%2Fuploads%2Fgit-blob-a14bdede861137a286a0bab3814fb01756db5df6%2Fcard-hooks.jpg?alt=media">card-hooks.jpg</a></td><td><a href="/quantum-hooks/fee-modules.md">Fee modules</a></td></tr><tr><td><strong>Launch extras</strong></td><td>Superposition and Time Dilation.</td><td><a href="https://3333211986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWu2Zj9LCnjL5ul1zbj2X%2Fuploads%2Fgit-blob-91cb57d49bf9a0401dcf2971f173899891c4e898%2Fextra-superposition.jpg?alt=media">extra-superposition.jpg</a></td><td><a href="/quantum-hooks/launch-extras.md">Launch extras</a></td></tr><tr><td><strong>Guarantees and risks</strong></td><td>What the program enforces, and what it can't.</td><td><a href="https://3333211986-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWu2Zj9LCnjL5ul1zbj2X%2Fuploads%2Fgit-blob-1ac5f8aa1837e20f1bb52823915b85d9a033ba8c%2Fmodule-fusion.jpg?alt=media">module-fusion.jpg</a></td><td><a href="/quantum-hooks/guarantees-and-risks.md">Guarantees and risks</a></td></tr></tbody></table>

<a href="https://www.quantpad.company/launch" class="button primary" data-icon="rocket">Launch with Quantum Hooks</a>


---

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