> 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/markdown.md). # Betting Phase #### Once the market is open, multiple participants can join in. Users connect their wallets and choose a side (**Yes** or **No**) to bet on. They stake their chosen currency (the market will indicate which currencies are accepted; many markets allow SOL, $POLYPUMP, or even both). The Polypump smart contract records each bet, updating the total stakes on each side. As bets accumulate, the odds (prices of Yes vs No shares) update in real-time according to the amounts staked, as described in the previous section. This phase continues until the market’s deadline is reached (or until an event occurs that would prematurely decide the outcome). Users can enter or exit positions while the market is open (though in the current version, bets are typically locked in until resolution; a future update might allow selling your position early on a secondary market). Throughout the betting phase, the question’s progress can be tracked (for example, if the prediction is about reaching a certain metric, users might watch live data to inform their bets). --- # 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/markdown.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.