> 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/why-daoi.md). # Why Daoi ## Why Daoi ### The problem is not deployment alone Many products can deploy a token. Far fewer products coordinate the full launch path: * who deploys the token * who receives and holds the funds * who creates LP * who opens trading * who closes launch-time permissions * who submits source verification * who turns raw chain state into usable public pages Daoi is built around that full path rather than around deployment only. ### Why token teams care If a platform only helps create a token contract, teams still need to solve: * fundraising custody * LP setup * permission shutdown * verification * public project presentation Daoi reduces that fragmentation by treating launch as an integrated system. ### Why developers care Open templates are useful, but unmanaged templates can break platform standards. Daoi addresses this by letting developers extend token logic without turning the platform into an uncontrolled collection of unrelated launch paths. The platform approach is: * developers can submit templates * templates are reviewed before they become public * registered templates continue to use platform launch rules * templates do not get to replace the platform’s fund custody and finalize model ### Why integrators care Wallets, bots, terminals, and data teams do not want to reverse-engineer every template as a separate protocol. Daoi aims to expose a stable platform structure: * stable factory system * stable project-to-token mapping * stable public API surfaces * stable finalized state transitions ### Where Daoi is different ### 1. Templates are extensions of the platform, not exceptions to it The platform is designed so new mechanisms can be onboarded without giving up the launch standard. ### 2. It focuses on post-launch state closure The system cares about what happens after fundraising is complete, not just whether project creation succeeded. ### 3. Deterministic deployment and verification are product capabilities Address planning and verification are part of the platform model, not side scripts that teams need to assemble later. ### 4. It leaves room for mechanism diversity without giving up protocol boundaries That balance is what makes template expansion sustainable. *** ## 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/why-daoi.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/why-daoi.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.