> For the complete documentation index, see [llms.txt](https://docs.0y.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.0y.world/markets/how-are-markets-resolved.md).

# How Are Markets Resolved

0Y Markets resolves markets using reliable external sources such as:

* Binance live feed API data
* Chainlink data dtreams
* other third-party providers (depending on market type)

At expiry, 0Y Markets checks the outcome based on the market’s defined rule (e.g., “price at timestamp”).

{% hint style="info" %}
Markets settle automatically at expiry — you don’t need to do anything.
{% endhint %}

***

#### Settlement outcome (what happens next)

Once a market is finalized:

* winning side receives payout to wallet balance
* losing side does not receive the staked amount back
* the market is marked as Resolved

(Unlike P2P systems, there is no user-proposed resolution bonding process; 0Y Markets resolves centrally based on predefined rules and data sources.)

***

#### Ben’s resolution example (clear timestamp)

Market: “BTC closes above 50,000 at 12:00:00 UTC”

* At 12:00:00 UTC, 0Y Markets checks the defined source(s)
* If the close is 50,120 → YES wins
* If 49,980 → NO wins


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.0y.world/markets/how-are-markets-resolved.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.