> 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.md). # RAKE Technical documentation for RAKE's launch, trading, vault, and execution systems. **One rake. Every side wins.** From tweet to harvest, nothing sits. RAKE is an independent launchpad on Robinhood Chain. It treats deployment as the start of a token lifecycle, not its final state. Pons V2 provides the launch venue and exposure to the Pons community. RAKE is not a subsidiary, wrapper, or feature inside Pons. It operates the systems surrounding that venue: RakeVault, routing, harvest, Echo confirmation, the leaderboard, and its execution interfaces. This distinction defines the protocol boundary. RAKE uses Pons V2 for launch exposure while operating its own post-launch mechanisms. It does not touch the Pons protocol's 30% side. {% hint style="info" %} RAKE connects launch exposure with fee collection, distribution, burns, execution, and visible token state. {% endhint %} ### What happens after launch Launching deploys a token. The system activity that follows includes accumulated fees, harvest, token interaction, and visibility. RAKE organizes these stages into one connected lifecycle. ``` Launch → Token becomes active → Fees accumulate → Anyone can harvest → Fees enter RakeVault → Fees distribute automatically → $RAKE and $PONS are market-bought and burned → Activity appears on the leaderboard → Users continue through supported interactions ``` Those interactions include trading, tipping, buying, burning, buyback, bridging, and prediction. RAKE therefore describes more than a deployment surface. It connects launch to the protocol actions that follow it. ### Two faces, one system #### X bot The RAKE X bot, [`@rake_agent`](https://x.com/rake_agent), is the conversational and mobile-first interface. It supports `launch`, `harvest`, `tip`, `swap`, `buy`, `burn`, `buyback`, `bridge`, and `predict`. Commands enter the same RAKE system used by the visual interface. For money-moving actions, the documented Echo confirmation process controls execution. #### dApp [`rakelaunch.xyz`](https://rakelaunch.xyz) is the visual interface for the leaderboard, token pages, the harvest panel, and the prediction market UI. It provides context around launched tokens and supported protocol activity. X and the dApp are not separate products. They are two interfaces into the same RAKE system. ``` X ↕ RAKE ↕ dApp ``` An action started through one interface can continue through the other where the system supports it. The interfaces offer different entry points, not separate protocol paths. ### The RAKE system | Component | Role | | ----------------- | ------------------------------------------------------ | | Launchpad | Deploys tokens through Pons V2 | | RakeVault | Receives and routes applicable creator-side fees | | Harvest | Permissionlessly pulls accumulated fees into RakeVault | | Router | Handles RAKE trading flows | | Echo | Provides exact confirmation for money-moving actions | | Leaderboard | Surfaces token activity and harvest state | | RWA Layer | Supports the defined stock-token assets | | Prediction Market | Creates YES/NO markets around supported assets | These components have distinct responsibilities. Together, they connect the launch venue to the lifecycle RAKE operates around it. ### Multi-verb execution RAKE is intentionally not limited to token launches. Its supported execution model contains nine verbs: `launch` · `harvest` · `swap` · `tip` · `buy` · `burn` · `buyback` · `bridge` · `predict` The system separates protocol-level actions from money-moving actions. This determines whether an action needs Echo confirmation. {% columns %} {% column %} #### No Echo * `launch` * `harvest` * `unclaimed` * `alive` * `predict` {% endcolumn %} {% column %} #### Echo required * `tip` * `swap` * `buy` * `burn` * `buyback` * `bridge` {% endcolumn %} {% endcolumns %} `unclaimed` and `alive` expose supported state queries. Echo-required actions move money or assets. The detailed command syntax and supported assets remain in the reference material. ### Harvest and the economic loop Harvest is central to RAKE's design because it moves accumulated fees into the protocol's distribution path. Anyone can trigger it. ``` @rake_agent harvest $MOON ``` Harvest pulls accumulated fees from the relevant curve, hook, and escrow sources into RakeVault. The vault then applies a fixed distribution to the creator-side fees it receives: ``` 70% → Creator wallet 15% → Market-buy $RAKE → Burn 15% → Market-buy $PONS → Burn ``` The burn activity belongs to the protocol fee flow. It is not a manually discretionary process. This loop ties post-launch fee accumulation to creator distribution and the documented buy-burn allocations. ### Execution safety Echo is a defining execution control for actions that move money or assets. Conversational text alone does not authorize those actions. ``` RAKE creates a draft → User replies with the exact same amount → Exact match confirms → Mismatch cancels ``` The confirmation window lasts 180 seconds. Echo is designed to protect against misclicks, typos, and prompt injection. The LLM layer cannot bypass Echo, infer missing amounts, or generate executable calldata. The parser and schema control execution. See [How RAKE Works](/rake/how-rake-works.md) for the documented mechanics. ### Visibility and state Every token launched through RAKE appears on the leaderboard. It is the system's visible state layer for launched-token activity and harvest-related metrics. The board exposes: * Trade volume, holder count, and total accumulated fees * $RAKE burned, $PONS burned, and the last harvest timestamp * Alive or dead status RAKE does not only execute actions. It also surfaces protocol and token activity without presenting that visibility as a safety, legitimacy, or outcome assessment. ### RWA and prediction RAKE supports the following stock tokens: `NVDA`, `GME`, `AAPL`, `TSLA`, and `SPY`. These assets can participate in supported tipping, swapping, and prediction-market flows. ``` @rake_agent predict NVDA >150 Friday ``` This creates a YES/NO prediction market around a defined outcome. Settlement details and market mechanics belong in the dedicated documentation. {% hint style="warning" %} These stock tokens are not real stock or shares. They provide no shareholder rights and are not offered to US or UK persons. {% endhint %} ### Architectural principle RAKE separates the launch venue from the protocol mechanisms around it. Pons V2 supplies launch exposure. RAKE owns and operates its vault, router, harvest system, Echo layer, and leaderboard. That boundary also applies to fees. RAKE operates the creator-side route that enters RakeVault. It deliberately does not touch the Pons protocol's 30% side. This is RAKE's independent architecture within the documented Pons V2 relationship. ### How to read this documentation Use the sections below based on the question you need to answer: * [Introduction](/rake/introduction.md) explains what RAKE is and why it exists. * [How RAKE Works](/rake/how-rake-works.md) covers launch, harvest, fee flow, and Echo. * [RAKE Ecosystem](/rake/rake-ecosystem.md) covers the X bot, dApp, leaderboard, and RakeVault. * [Trading & Utility](/rake/trading-and-utility.md) covers swap, tip, buy, burn, buyback, and bridge. * [RWA & Prediction](/rake/rwa-and-prediction.md) covers stock-token interactions and prediction markets. * [Security](/rake/security.md) covers no-rug controls, smart-contract controls, and execution safety. * [Tokenomics](/rake/tokenomics.md) covers $RAKE, fee distribution, and burns. * [Roadmap](/rake/roadmap.md) presents the ordered implementation milestones. * [Commands & Assets](/rake/commands-and-assets.md) provides the supported command and asset reference. * [Disclaimers](/rake/disclaimers.md) states the project's boundaries and disclosures. RAKE connects launch, harvest, execution, visibility, and asset interaction through one system. Both X and the dApp expose that system as the technical documentation continues below. --- # 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.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.