> For the complete documentation index, see [llms.txt](https://docs.yamata.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yamata.io/prediction-markets/participating-in-markets.md). # Participating in Markets ### Finding Markets **Public Markets Page** * Browse verified markets that met liquidity threshold * Filter by category, token, timeline * Sort by volume, activity, closing soon **Wild West Zone** * Discover new markets building liquidity * Higher risk, potential for better early odds * Direct links from market creators ### Making a Commitment 1. **Select Market** * Review event description * Check timeline and parameters * Analyze current distribution 2. **Choose outcome** * Select your predicted outcome * See current odds and commitments 3. **Enter amount** * Specify commitment amount * Preview beta weight based on timing (if enabled) * Review estimated returns if correct 4. **Approve & Commit** * Approve token spending (first time only) * Submit commitment transaction * Receive ERC-1155 position token 5. **Manage Position** * Hold until resolution to claim rewards * Monitor market activity * Prepare for resolution period --- # 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.yamata.io/prediction-markets/participating-in-markets.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.