> 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/introduction.md). # Introduction RAKE's position on Robinhood Chain, its purpose, and its relationship to Pons V2. RAKE treats a token launch as a beginning, not a finish line. Deployment creates a token. The work that follows creates its ongoing context. Trading activity, accumulated fees, harvesting, burns, visibility, and interaction all shape that context. RAKE starts with token launches, then connects the activity that follows. It frames launch as the entry point to a wider ecosystem, rather than an isolated event. ### RAKE's position RAKE is an independent ecosystem on Robinhood Chain. It uses Pons V2 as the launch venue for exposure to the Pons community. That relationship has clear boundaries. **Pons V2 is the venue. RAKE is the independent system around the launch experience.** RAKE operates its own vault, harvest, burn, Echo, and leaderboard mechanisms. RAKE is not a Pons V2 product or partner. It does not claim official affiliation with Pons V2. ### Beyond the launch A live token enters a longer lifecycle. It can generate activity and fees. Fees can be harvested. Harvesting can lead to distribution and burns. Those events become visible through the ecosystem, then support further interaction. This is not a single forced sequence. It is RAKE's broader view of what surrounds a token after deployment: `launch` → `activity` → `fees` → `harvest` → `burns` → `visibility` → `interaction` The lifecycle gives post-launch actions a shared context. RAKE connects those actions without treating them as replacements for deployment. ### Two interfaces, one system RAKE meets users through two connected interfaces. The X bot, `@rake_agent`, provides a conversational and mobile-first path for supported actions. The dApp provides a visual path for the leaderboard, token pages, harvest panel, and prediction market. > **Two faces, one lane.** These interfaces are not separate products. They expose the same RAKE ecosystem from different starting points. An action can begin through X and continue in the dApp. It can also begin in the dApp and continue through X. ### A broader set of actions RAKE is designed for more than deployment. Its action model includes: * `launch`, `harvest`, and `swap` * `tip`, `buy`, and `burn` * `buyback`, `bridge`, and `predict` Each action has a distinct role and execution path. The following sections define their mechanics, constraints, and supported assets. Visibility is part of that model. Every token launched through RAKE appears on the real-time leaderboard. It gives the ecosystem a shared view of trading activity, holders, accumulated fees, burns, harvest timing, and alive or dead status. The leaderboard is a record of tracked ecosystem activity. It is not a safety assessment or outcome guarantee. ### What this documentation covers The pages ahead move from RAKE's purpose into its mechanics and ecosystem. They cover trading utilities, RWA and prediction, security, tokenomics, the roadmap, commands, supported assets, and disclaimers. --- # 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/introduction.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.