> For the complete documentation index, see [llms.txt](https://peeps-2.gitbook.io/peeps-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://peeps-2.gitbook.io/peeps-docs/peeps-whitepaper/vision/mission.md). # mission ## Let the people launch PEEPS takes inspiration from the democratic spirit behind **“Let the people trade.”** The mission is to lower the barrier between an idea and an on-chain community. The platform is being built around five principles: ### Open access Token creation should not require private connections, a large budget or specialist coding knowledge. ### Transparent mechanics Launch conditions, fees, contract addresses and graduation rules should be visible before a user signs a transaction. ### Community before insiders PEEPS is designed for fair access and public participation, not hidden allocations or undisclosed advantages. ### Creators should keep building The economic model is intended to reward creators for sustained community work, subject to the final published fee schedule. ### Platform activity should strengthen the ecosystem A disclosed portion of launchpad fees supports the $PEEPS ecosystem through measures such as buybacks, token burns and ecosystem marketing. These activities do not guarantee any increase in price, liquidity or value. --- # 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://peeps-2.gitbook.io/peeps-docs/peeps-whitepaper/vision/mission.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.