> 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/frequented-asked-questions-faq.md).

# Frequented Asked Questions (FAQ)

### Q: What happens if a market never reaches the liquidity threshold?

A: It remains in the Wild West zone indefinitely. Participants can still commit and resolve as normal—it simply won't appear on the Public Markets page.

### Q: Can I cancel my commitment?

A: No direct cancellation is possible. Position tokens are non-transferable, so you must hold your position until resolution.

### Q: What if the market creator submits a wrong result?

A: Anyone can challenge the result during the 24-hour challenge period by staking tokens. If the challenge is valid, the challenger is rewarded and the result is corrected.

### Q: How are subjective events resolved?

A: Yamata works best with objectively verifiable events. Subjective events may be challenged and require community consensus or may be cancelled.

### Q: Can I create markets on any event?

A: Yes, but markets must comply with terms of service. Illegal activities, violence, or clearly unethical events are prohibited and may be flagged.

### Q: What tokens can I use?

A: Any ERC-20 token can be used for commitments. Popular choices include USDC, USDT, and DAI.

### Q: Are there limits on market creation?

A: Yes, quota management prevents spam. Limits based on account age, reputation, and frequency.

### Q: Can I create markets with more than 2 outcomes?

A: Absolutely! Markets support 2 to unlimited outcomes (practical limit \~50 for UX).


---

# 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/frequented-asked-questions-faq.md?ask=<question>&goal=<endgoal>
```

`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.