> For the complete documentation index, see [llms.txt](https://docs.rakelaunch.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rakelaunch.xyz/rake/how-rake-works/launch.md). # Launch RAKE's launch flow and Pons V2's role as the venue for launch exposure. ## Launch into the RAKE lifecycle Launch creates the starting point for a token's fee path through RAKE. The token deploys on Pons V2, which serves as the launch venue, while RakeVault receives the creator-side fees used later in the lifecycle. ``` @rake_agent launch $TICKER "Name" pair ETH ``` ### Launch sequence ``` Launch request ↓ Token deployment on Pons V2 ↓ Fee recipient = RakeVault ↓ Token enters RAKE ecosystem ↓ Token appears on leaderboard ↓ Fees can later be harvested ``` When a launch is initiated, RAKE deploys the token on Pons V2. It sets the fee recipient to RakeVault. Fees therefore do not route directly to the creator. This configuration makes the later lifecycle possible. Accumulated fees can be harvested into RakeVault, where the fixed creator-side distribution is applied. The launched token also appears on the RAKE leaderboard. The leaderboard records the token's presence in the RAKE ecosystem. It does not change the launch or fee-routing mechanics. ### Launch interfaces RAKE supports two interfaces for initiating the same system flow: * **X bot** ``` @rake_agent launch $MOON "MoonShot" pair ETH ``` * **dApp** ``` rakelaunch.xyz/launch → fill form → deploy ``` Both interfaces lead to deployment on Pons V2 with RakeVault as the fee recipient. The interface changes how the request starts. It does not create a separate fee path. Once fees accumulate, [Harvest](/rake/how-rake-works/harvest.md) can move them into RakeVault. --- # 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.rakelaunch.xyz/rake/how-rake-works/launch.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.