> For the complete documentation index, see [llms.txt](https://docs.polypump.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.polypump.app/documentation/polypump-process/editor.md). # Market Creation ### The process begins with a user (or developer) creating a new prediction market. The creator formulates a yes/no question about a specific token or event, sets an expiration time, and attaches the relevant **token address**. Attaching the token’s address allows Polypump’s systems to monitor that token’s data for the condition. Upon creation, the creator stakes an initial amount of currency (which can be SOL or $POLYPUMP) into the market to open it. This initial stake can serve as the first bet (for example, the creator might stake on “Yes” if they believe the event will happen) and also provides initial liquidity so that other users can start betting against it. The market is now live and visible to the community. --- # 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.polypump.app/documentation/polypump-process/editor.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.