> 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/launch-extras.md).
# Launch extras
Optional extras for a Quantum launch: split your creator share, or lock part of your dev buy.
Superposition
Split your creator share with up to four extra wallets.
## Superposition
Split the creator share across up to four extra wallets, for example a co-founder, an artist or a community treasury.
Each wallet's share is fixed at launch. In every pulse, the Superposition wallets are paid their share of the creator slice first, and the launcher gets the rest.
## Time Dilation
Lock part of your dev buy with a cliff and linear vesting. Locked tokens can only be released to you, on schedule.
* By default, the Launch page locks 50% of the dev buy with a 7-day cliff and 90 days of vesting.
* The cliff must end before vesting finishes.
* Vesting lasts at least one day and at most four years.
The lock is applied in the launch flow right after the coin is created.
{% hint style="warning" %}
Like the hook allocation, Superposition wallets and Time Dilation schedules can't be changed after launch.
{% 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/launch-extras.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.
