> 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/using-yamata/predictions-market/best-practices.md). # Best Practices ### For Market Creators **Do**: * Create clear, unambiguous events with verifiable outcomes * Set reasonable timelines giving participants time to commit * Promote your market actively to reach liquidity threshold * Provide context in descriptions to attract participants * Choose popular stablecoins (USDC, USDT) for broader appeal **Don't**: * Avoid subjective outcomes that cannot be objectively resolved * Don't set close times too close to event occurrence * Don't create spam markets (rate limiting will block you) ### For Participants **Do**: * Research the event before committing * Commit early to maximize beta rewards if confident (when enabled) * Diversify across multiple markets and outcomes * Monitor positions and market activity * Verify market parameters before committing **Don't**: * Don't commit to unclear events with ambiguous outcomes * Don't risk more than you can afford to lose * Don't ignore timelines and miss commitment windows --- # 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/using-yamata/predictions-market/best-practices.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.