> For the complete documentation index, see [llms.txt](https://docs.probly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.probly.com/fees-and-settlement/market-resolution.md).
# Market Resolution
How markets are resolved on Probly.
Every market has a defined **resolution condition** and **deadline**. When the deadline passes, the market is resolved against an objective data source — winning shares redeem for **$1.00** each, losing shares go to **$0**.
## Market Lifecycle
## Resolution Process
### 1. Deadline Passes
Each market has a specific deadline (e.g. **Feb 16, 17:00 UTC**). No new trades are accepted after that moment.
### 2. Oracle Reports the Outcome
The designated oracle source provides the verified result:
* **Automated price feeds** (crypto, stocks, numeric data) resolve immediately at the deadline
* **Manual resolution** (sports, politics, custom events) typically takes **24–72 hours**, depending on event complexity and data availability
{% hint style="info" %}
The **exact resolution source and criteria** are published on each market page. Always read them before trading — they are the rulebook the market is judged by.
{% endhint %}
### 3. Payouts Settle
* **Winning** shares redeem for **$1.00 USDC** each
* **Losing** shares are worth **$0**
* Payouts settle on-chain automatically — no claim step
## Open Orders at the Deadline
When the deadline passes:
* All open limit orders are **cancelled automatically**
* Locked USDC (buy orders) returns to your available balance
* Locked shares (sell orders) return to your position
## Payout Math
Every **1 YES + 1 NO** pair was collateralized by $1.00 USDC — at resolution that dollar flows entirely to the winning side:
| You held | Market resolved | You get |
| -------- | --------------- | ------------------------- |
| 100 YES | YES | 100 × $1.00 = **$100.00** |
| 100 YES | NO | $0 |
| 100 NO | NO | 100 × $1.00 = **$100.00** |
| 100 NO | YES | $0 |
For **category markets**, only YES on the winning outcome pays $1.00; every other YES resolves to $0 (NO is the mirror image). See [Category Markets](/markets-and-trading/category-markets.md).
## Resolutions Are Final
{% hint style="warning" %}
A resolution **consistent with the published rules is final** — disagreeing with the real-world outcome does not qualify a position for a refund. Read the resolution criteria on the market page before trading.
{% endhint %}
In rare cases — a resolution source becoming unavailable, an event cancelled or indefinitely postponed, a materially ambiguous outcome, or a critical setup error — a market may be **voided**. See [Refund Policy](/resources/refund-policy.md) for when this applies, and the [Terms of Use](broken://pages/4u1zW8xhLNtrPaXxfwaR) for the binding dispute procedure.
## Related
* [Refund Policy](/resources/refund-policy.md) — when markets may be voided
* [Terms of Use](broken://pages/4u1zW8xhLNtrPaXxfwaR) — binding rules and dispute procedure
* [Merging & Splitting Shares](/markets-and-trading/merging-and-splitting.md) — convert between USDC and share pairs
---
# 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.probly.com/fees-and-settlement/market-resolution.md?ask=&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.
