> 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/how-launching-works.md). # How Launching Works ## How Launching Works This page explains the launch process from a product perspective. For the deeper call chain, see Launch Flow Internals. ### 1. A team creates a project On the create page, a team submits: * token name and symbol * total supply * presale price * soft cap and hard cap * per-transaction and per-wallet limits * end time * logo, description, and links * a selected template ### 2. The platform creates project components The project is created through the factory system, which coordinates: * token * vault * presale ### 3. Participants join the presale Users contribute BNB to the presale path. Funds are held in custody and the presale state advances according to platform rules. ### 4. The project reaches finalize When launch conditions are met, the finalize path handles the market transition: * platform fee handling * LP creation * pair discovery * market configuration * LP burn * trading enablement * permission shutdown ### 5. The token moves into the public market phase Once finalize is complete, the token page becomes the primary market-facing page with market data, liquidity data, and trade history. ### 6. Verification and public state follow The backend verification flow then picks up finalized tokens and pushes them into the source verification pipeline. ### Why this matters The key idea is that projects do not leave the platform at the moment they are created. They stay inside a coordinated lifecycle until they reach a standardized public market state. *** ## 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/en/how-launching-works.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/how-launching-works.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.