> 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/market-lifecycle-and-states.md).

# Market Lifecycle & States

Every market on Yamata progresses through defined states:

### State Flow

<figure><img src="/files/mg777Y7dYmRfYiBawX1k" alt=""><figcaption></figcaption></figure>

### State Definitions

1. #### Created

* Market parameters set
* Awaiting opening time
* No commitments accepted yet

2. ### Open

* Commitments accepted
* Position tokens minted
* Beta decreasing over time (if enabled)

3. ### Closed

* No new commitments
* Awaiting resolution time
* Event may still be ongoing

4. ### Resolved

* Market creator has submitted result
* 24-hour challenge period active
* Preparing for payouts

5. ### Payouts

* Winners can claim rewards
* Beta-weighted distribution (if enabled)
* Position tokens burned on claim

6. ### Cancelled/Refunds

* Market flagged or unresolvable
* All participants refunded
* No winners/losers


---

# 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/market-lifecycle-and-states.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.