> For the complete documentation index, see [llms.txt](https://takes.gitbook.io/takes-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://takes.gitbook.io/takes-docs/technical-design/launch-sequence.md). # Launch sequence Publication stores a complete basket and immutable version without funding. Pool creation fixes that version and funds the seed. Activation prepares the trading account. ```mermaid sequenceDiagram participant U as Creator participant A as Takes app participant F as Factory and token participant S as Takes services participant H as Trading account U->>A: Publish complete basket and icon U->>A: Choose version, network, asset leverage and seed A-->>U: Prepare creation transaction U->>F: Create token and deposit seed A->>F: Confirm matching creation S->>F: Pair hub or activate native hub F->>H: Process seed mint S->>H: Confirm account setup and trading permissions S-->>A: Mark token live S->>F: Deliver settled seed tokens to creator ``` Before creation, Takes checks markets, basket limits, fixed percentage policy, signed settlement fees and minimum net seed. Afterward, it checks the successful factory transaction against the deployer and immutable reviewed strategy. Arc, Ethereum, Base, Arbitrum, and Monad need a separate HyperEVM hub and one-time pairing. HyperEVM activates the token's own account. The seed request starts execution during pairing or activation and follows the same [fee and transfer rules](/takes-docs/reference/fees-and-limits.md#fees-and-limits) as later mints. Setup progress is saved and rechecked before repeating actions. Temporary failures retry; invalid setup or repeated failure needs operator attention. Cancelling the accepted seed prevents normal activation. Publishing another basket version does not change or undo a created pool. Live means setup completed, not that target trades are guaranteed to have filled. See [Roles and permissions](/takes-docs/security-and-trust/roles-and-permissions.md#roles-and-permissions). --- # 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://takes.gitbook.io/takes-docs/technical-design/launch-sequence.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.