> For the complete documentation index, see [llms.txt](https://sply-1.gitbook.io/sply/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sply-1.gitbook.io/sply/launch-flow-internals.md). # Launch Flow Internals ## Launch Flow Internals This page describes the Daoi launch flow from the perspective of protocol execution. ### 1. The frontend encodes a launch request The create page encodes the project configuration and template parameters and submits the request through the factory path. ### 2. TemplateFactory performs template routing `TemplateFactory` determines which launch route applies: * built-in template path * approved developer template path * platform-managed custom core path * developer self-deployed core path The platform turns template choice into the correct contract execution path. ### 3. LaunchFactory creates the project components `LaunchFactory` creates and wires together: * token * vault * presale Depending on the template route, token deployment can use the standard token deployer, the platform custom core `CREATE2` path, or a validated developer-supplied core. ### 4. Project setup aligns supply and fundraising logic During setup, `LaunchFactory` transfers the required project token supply into the presale path and links the project contracts together. The purpose is not just initialization. It is to make the fundraising formula and the later finalize path line up. ### 5. Token hooks connect the token core to platform lifecycle The platform calls token-side hooks such as presale and market-related configuration hooks so the token core is attached to the platform lifecycle instead of floating outside it. ### 6. Participation advances the presale When a user participates: * BNB is moved into custody * presale progress advances * token distribution logic is applied through the project formula ### 7. Finalize moves the project into market state Finalize is the critical transition. It coordinates: * fee handling * LP creation * pair discovery * market configuration * LP burn * trading enablement * lock actions * temporary permission closure * presale address cleanup ### 8. Backend watchers continue the pipeline Once finalized, backend watchers enqueue the token for verification and keep the public surfaces in sync with the project’s new phase. ### Why the internal flow matters Without this structure, templates would effectively become independent launch systems. Daoi is designed so templates extend token logic while the platform keeps control over the fundraising and market transition lifecycle. *** ## Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://sply.fun/daoi-docs-import/architecture-and-components/launch-flow-internals.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://sply-1.gitbook.io/sply/launch-flow-internals.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.