> 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/what-makes-rake-different.md). # What Makes RAKE Different The boundaries between RAKE's protocol-owned systems and Pons V2's launch-venue role. RAKE connects launch, post-launch activity, visibility, and execution through one ecosystem. Its design has four defining components. ### 1. Independent launchpad RAKE operates independently on Robinhood Chain. Pons V2 serves as the launch venue for exposure to the Pons community. Using Pons V2 as a venue does not make RAKE part of the Pons protocol. RAKE owns its vault, router, Echo engine, and leaderboard. It does not touch the Pons protocol 30% side. RAKE does not claim to be an official Pons product or partner. ### 2. Two faces: X bot and dApp Users can launch through X or through the dApp. Both routes reach the same RAKE infrastructure. ``` @rake_agent launch $MOON "MoonShot" pair ETH rakelaunch.xyz/launch → fill form → deploy ``` The X bot is mobile-first. The dApp is visual-first. Together, they provide two interfaces for the same RAKE actions. ### 3. Real-time leaderboard Every token launched through RAKE appears on the real-time leaderboard. It provides a visible view of token activity and the wider ecosystem. The leaderboard tracks: * Trade volume and holder count * Total fees accumulated and the last harvest timestamp * $RAKE burned, $PONS burned, and alive/dead status This gives holders a shared view of the information associated with each launched token. It does not represent a safety assessment or guarantee an outcome. ### 4. Multi-verb model RAKE is not limited to deployment. Its supported action model includes: `launch` · `harvest` · `swap` · `tip` · `buy` · `burn` · `buyback` · `bridge` · `predict` Each verb serves a different part of the ecosystem. The later sections define their execution mechanics and constraints. Together, these components connect launch with post-launch activity, visibility, and execution. --- # 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/what-makes-rake-different.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.