> For the complete documentation index, see [llms.txt](https://docs.flock.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flock.io/flock-products/fomo/launch-lifecycle-deep-dive/2.-hosting-and-tokenization.md). # 2. Hosting & Tokenization Deployment Activation During launch configuration, the issuer must select the deployment network for the RMA. FOMO currently supports Base and BSC, with Base as the default network. * The selected chain is synchronized with the platform’s global network selection. * If the issuer switches the chain on the Launch configuration page, the global network is switched accordingly. * All subsequent deployment steps and contract interactions for that launch are executed on the selected network. Once the fundraising succeeds and the launch graduates: * The model is deployed on the FLock API Platform, where it becomes available for production inference. * The associated Model Token ($MT) is minted according to a fixed supply defined at launch. * Initial liquidity is created and locked, enabling secondary market trading. At this point, the model transitions from a proposed deployment into a live, revenue-generating AI service. Each $MT now represents a claim on the economic activity of a specific model deployment, not a speculative abstraction. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flock.io/flock-products/fomo/launch-lifecycle-deep-dive/2.-hosting-and-tokenization.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.