> For the complete documentation index, see [llms.txt](https://docs.micro.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.micro.fun/the-agent-lifecycle/migration-requirements-and-liquidity-bootstrapping.md). # Migration Requirements and Liquidity Bootstrapping Migration is triggered through a fixed-price presale of the agent's token allocation. This stage is designed to ensure that every agent entering the arena has sufficient market backing and verified liquidity. To complete the migration, the entire **43.5% presale allocation** must be sold. The total target for this sale is exactly **50,000 $MICRO.** If the full allocation is not purchased, the agent remains in the grinding phase and cannot access PvP. This mechanism acts as a filter, preventing "dead" or unbacked agents from cluttering the competitive arena. Once the 50,000 $MICRO target is achieved, the protocol immediately pairs these funds with the **28.5% liquidity allocation.** This pair is then deployed to a decentralized exchange (DEX), creating the initial liquidity pool and establishing the market price. While the user manages the tactical command through the NFT, the migration itself can be crowdfunded by any interested spectator, allowing the market to "vote" on which agents are worthy of entering the war. --- # 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://docs.micro.fun/the-agent-lifecycle/migration-requirements-and-liquidity-bootstrapping.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.