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

# Resolution

Resolution is the process by which an oracle submits the outcome of a market on-chain. It is the most critical operation in the protocol: once an outcome is submitted and confirmed, winning share holders can claim their USDC and losing shares become worthless.

The resolution criteria for every market are stored in an on-chain `ancillary_data` field at creation time and are immutable. The oracle resolves strictly against those criteria. There is no ambiguity about what "winning" means after the market is created.

## Beta: trusted multisig oracle

During private and public beta, all markets are resolved by the Footymarket team multisig. The multisig is a 3-of-5 configuration implemented via Squads Protocol on Solana.

**Resolution process:**

1. The event concludes (match ends, transfer completes, season finishes)
2. The team cross-references the outcome across multiple official data sources
3. The multisig submits the `resolve_market` instruction with the confirmed outcome
4. The on-chain program records the outcome and transitions the market to Resolved status
5. Winning share holders can immediately call `claim_winnings`

**Target resolution time**: within 30 minutes of the final whistle for match markets.

All resolution transactions are on-chain and publicly auditable. Every market's resolution page links to the on-chain transaction.

### Data sources used for resolution

| League or competition | Primary source              | Secondary source                            |
| --------------------- | --------------------------- | ------------------------------------------- |
| Premier League        | Premier League official API | BBC Sport                                   |
| UEFA Champions League | UEFA official data          | Sky Sports                                  |
| La Liga               | LaLiga official website     | ESPN                                        |
| Serie A               | Lega Serie A official       | Sky Sport Italia                            |
| Bundesliga            | DFL official data           | Sky Sport DE                                |
| Transfers             | Official club announcements | Fabrizio Romano / confirmed agency releases |

The team uses at minimum two independent sources before submitting a resolution. If sources conflict, resolution is delayed until the discrepancy is resolved or the market is voided.

### Missed resolution deadline

If the Footymarket team does not submit a resolution by the resolution deadline, the following applies:

* The market remains in Locked status and continues to accrue the deadline
* A grace period of 4 hours applies before a market can be escalated
* If resolution is still not submitted after the grace period, users can raise the market for review via the Footymarket Discord
* If no resolution is submitted within 48 hours of the deadline, the market is voided and all collateral is returned pro-rata

This policy protects traders in the event of operational issues on the team's side.

### Disputes

If you believe a market was resolved incorrectly, raise a dispute through the Footymarket Discord or by email. Include the market ID, the outcome you believe is correct, and the source that supports your position. The team reviews all disputes within 24 hours.

{% hint style="info" %}
The beta multisig is a deliberate choice. Speed, simplicity, and reliability matter more than full decentralisation at launch. The transparency of on-chain resolution provides accountability even with a trusted oracle: every resolution is publicly verifiable and cannot be altered after submission.
{% endhint %}

## Post-beta: optimistic oracle

After beta, Footymarket transitions to a custom optimistic oracle program. The optimistic model shifts resolution from a trusted authority to a bonded, community-driven process.

### How it works

1. Any bonded user can propose the outcome of a resolved market
2. The proposal enters a **24-hour challenge window**. If no challenge is submitted, the proposal is accepted as final.
3. If challenged, the dispute escalates to a bonded arbitration committee
4. The committee votes on-chain. The majority outcome is final.
5. Incorrect proposers lose their bond. Successful challengers earn a reward from the bond pool.

### Why optimistic

The optimistic model is efficient: the common case (correct resolution) settles in 24 hours with minimal cost. The dispute mechanism exists for the rare case of an incorrect or contested resolution. The bond requirement ensures that proposers have economic skin in the game.

### Resolution criteria and ancillary data

Each market's resolution criteria are defined at creation time and stored in the `ancillary_data` field of the Market account. The optimistic oracle evaluates proposals strictly against these criteria. Vague or ambiguous criteria are a market quality problem, not a resolution problem, which is why the curation layer enforces quality before markets go live.


---

# 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:

```
GET https://docs.footymarket.xyz/markets/resolution.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
