> 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/fee-modules.md).
# Fee modules
The four places a Quantum coin's creator fees can go: Creator share, Quantum Burn, Entanglement and Fusion.
Each fee pulse is split across four modules, by the allocation the launcher fixed at launch. The allocation always adds up to 100%.
## Creator share
Sent to the launcher wallet in the same pulse that collects the fees. If [Superposition](/quantum-hooks/launch-extras.md#superposition) wallets are set, they are paid their fixed share of this slice first.
## Quantum Burn
Accumulates in the coin's burn reserve. The keeper spends it in capped buys (on the Meteora bonding curve before graduation, on its DAMM v2 pool after) and burns every token bought in the same transaction. This shrinks the coin's supply.
If the keeper stalls, anyone can run the burn after a grace period.
## Entanglement
Accumulates in the holder reserve.
{% stepper %}
{% step %}
### Snapshot
About once a day, and never more often than every 20 hours, the keeper snapshots wallet balances and posts a merkle root for the epoch on-chain.
{% endstep %}
{% step %}
### Delay
The epoch's claims open 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.
{% endstep %}
{% step %}
### Claim
Holders claim their SOL from the coin page until the epoch expires, 30 days after posting.
{% endstep %}
{% step %}
### Roll over
Unclaimed SOL rolls into the next epoch.
{% endstep %}
{% endstepper %}
## Fusion
Before graduation, the Fusion reserve simply accumulates. After graduation, it buys tokens and adds both sides to the well's Meteora DAMM v2 position, permanently locked.
{% hint style="info" %}
The program has no instruction to withdraw Fusion liquidity. Once added, it can never be removed.
{% 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/fee-modules.md?ask=&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.
