> 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/protocol-integration.md). # Protocol Integration ## Protocol Integration This page is for wallets, bots, terminals, indexers, and third-party data consumers. ### Network * Network: `BNB Smart Chain Mainnet` * Chain ID: `56` See Deployed Contract Addresses for the current live addresses. ### Primary on-chain entry points The most important contracts for integrations are: * `LaunchFactory` * `TemplateFactory` * `FactoryAdmin` These define where projects are created, how templates are routed, and which template set is official. ### Project-centric data model Integrations should think in terms of project objects rather than raw token discovery. The stable model is: * project id * presale * token * vault * pair This is the same relationship the platform uses in its frontend and backend aggregation. ### Prefer platform APIs for public surfaces If your goal is to display: * project lists * project detail pages * token market views * recent trade lists it is usually better to start with Daoi’s APIs rather than rebuilding every view directly from chain events. ### When direct chain reads still matter Direct reads are still appropriate when: * you operate your own indexer * you need final chain truth * you build monitoring and alerting * you validate project status independently ### Integration priorities The most useful checks are: * whether a project came from the official factory * whether a template came from the official registry * whether the project has finalized * whether a pair exists * whether the token has entered 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://docs.daoi.fun/developer-template-guide/protocol-integration.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/protocol-integration.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.