> 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/faq/settlement-oracle-and-disputes.md).

# Settlement, Oracle, and Disputes

#### How are markets resolved?

0Y resolves markets using the data sources listed in the market rules, including:

* Binance live feed API data
* Bybit websocket data stream
* Chainlink data streams
* and other third-party sources when needed
* Additional other data sourced used as oracle will be added in the near future

#### When do markets settle?

Markets settle automatically at the specified expiry/resolution time.

#### What if the data feed is wrong or unavailable?

If there’s a data quality dispute (missing, inconsistent, or unreliable data), 0Y may refund the market.

#### What is 0Y’s refund policy?

If a market cannot be resolved reliably due to data quality issues, 0Y will:

✅ Refund all traders for that specific market (returning stakes).

No side is declared the winner.

#### Does refund include blockchain gas fees?

Refunds generally return your stake for that market. Network gas fees paid to the blockchain are typically not refundable.


---

# 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/faq/settlement-oracle-and-disputes.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.