> 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/verification-and-public-state.md). # Verification and Public State ## Verification and Public State This page explains how finalized projects move into verified public state and which chain inputs external platforms commonly rely on. ### 1. Finalize completes the launch transition A project is not truly public just because it was created. It becomes public in the platform sense when finalize has completed and the token has entered its standardized market state. ### 2. The backend watches finalized projects Backend watchers scan finalized projects and enqueue their tokens for source verification. Verification is therefore part of the launch pipeline rather than a disconnected manual step. ### 3. source-verify resolves the correct profile The verification service supports the standard token path and can also resolve verification metadata from compatible custom token cores. It determines: * source path * contract name * matching build info before submitting a verification request. ### 4. Public state is built from on-chain inputs The platform cannot force third-party scanners to refresh instantly, but it can make sure the chain state it produces is consistent. The important inputs include: * source verified * owner closed out * presale address cleared * key launch permissions locked * LP burned * trading enabled ### 5. Why this matters If a platform stops at deployment and fundraising, public status becomes an afterthought. Daoi treats verified, market-ready state as part of the product flow. ### 6. Interpreting third-party displays External platforms may cache differently or interpret inputs differently. Daoi’s job is to keep the on-chain state path and verification path consistent so those platforms have stable inputs to read. *** ## 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/verification-and-public-state.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/verification-and-public-state.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.