> For the complete documentation index, see [llms.txt](https://docs.esvelocity.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.esvelocity.fun/readme.md). # Overview **Escape Velocity** is an Ethereum-native launch and momentum protocol designed to solve the most fragile phase of token markets: **the period after launch**. Most platforms optimize for creation.\ Escape Velocity optimizes for **continuity**. By combining a standardized token factory, native creator fees, and an automated momentum engine, Escape Velocity converts on-chain activity into **self-sustaining market dynamics**. > Launch is not enough. Momentum is a primitive. ### What Escape Velocity Does * Launches tokens under strict, predictable rules * Enforces native creator fees * Automatically converts those fees into market activity * Gradually removes itself as markets stabilize Escape Velocity is not a growth hack.\ It is **infrastructure for market survival**. --- # 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.esvelocity.fun/readme.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.