> For the complete documentation index, see [llms.txt](https://limelight-1.gitbook.io/limelight-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://limelight-1.gitbook.io/limelight-docs/for-creators/resolution-sources.md).

# Resolution Sources

Every market needs a definitive source — the data feed or publication that determines the final outcome. This page covers how Limelight resolves markets and lists approved external sources by category.

## Price Markets: Pyth On-Chain

For **price, crypto, FX, and commodity** markets, Limelight resolves against **Pyth** price feeds read on-chain in the resolution transaction.

Pyth is a decentralized, first-party-sourced oracle **integrated on Movement** (it is not a built-in, chain-level oracle). It's a **pull oracle**: the resolver submits a fresh price update (paying a small update fee) and reads the price **in the same transaction**, so resolution uses a verifiable on-chain value rather than a manually entered number. Pyth covers crypto, equities, FX, and commodities.

This makes "Will BTC be above $X at time T?"-style markets resolve cleanly with minimal manual adjudication. A short dispute window still follows each resolution — see [Market Lifecycle & Disputes](/limelight-docs/knowledge-base/market-lifecycle-and-disputes.md).

## Event Markets: External Sources

For events that aren't a price (politics, sports, culture, science, and so on), pick **1–3 verifiable, publicly accessible sources**. The first is authoritative; the rest serve as fallbacks.

**Principles**

* **Specific over generic.** Link to the exact coin page, tournament page, or data endpoint — not the homepage.
* **Public and verifiable.** Anyone should be able to check the outcome independently.
* **Timestamp-aware.** Prefer sources that expose timestamps, not just current values.
* **Original over aggregated.** Prefer primary sources over news rewrites.

## Approved Sources by Category

<table><thead><tr><th width="192">Category</th><th>Primary sources</th><th>Specify</th></tr></thead><tbody><tr><td>Crypto (price)</td><td>Pyth (canonical); CoinGecko, exchange APIs as cross-checks</td><td>Which pair, price type, whether flash wicks count</td></tr><tr><td>Sports</td><td>ESPN, official league sites, tournament pages</td><td>Overtime? forfeits? regulation vs full game? reschedules?</td></tr><tr><td>Political / News</td><td>Reuters, AP, BBC, Bloomberg; official government pages</td><td>"Announcement" vs "implementation"? multi-source confirmation?</td></tr><tr><td>Economy</td><td>SEC EDGAR, Bloomberg, WSJ, company IR, FRED</td><td>IPO = trading not S-1; GAAP vs non-GAAP; revisions</td></tr><tr><td>Science</td><td>NASA/ESA/JAXA; Nature, Science; CERN, NIH, WHO, USGS</td><td>Define "success"; press release vs peer-reviewed; delays</td></tr><tr><td>Tech</td><td>Official blogs, press releases, keynotes; SEC filings; GitHub releases</td><td>Announced vs shipped vs GA; region rollouts; betas</td></tr><tr><td>E-Sports</td><td>Liquipedia, HLTV, VLR.gg; organizer pages (Riot, Valve, ESL)</td><td>Series format; forfeits/DQs; roster lock</td></tr><tr><td>Entertainment</td><td>Box Office Mojo, Billboard, IMDb Pro; awards body sites</td><td>Domestic vs worldwide; which chart; audited vs estimate</td></tr><tr><td>Culture / Social</td><td>Direct post/video URLs; official account pages</td><td>Do bot views count? what if the post is deleted?</td></tr></tbody></table>

**Example (sports):** "Resolves Chelsea Win if the Premier League official site records Chelsea as the winner of the Chelsea vs Manchester United fixture on 2026-04-18. Draws and Man United wins resolve as Other Result. If rescheduled past expiry, market voids."

**Example (political):** "Resolves Yes if Reuters and AP both report, by 2026-06-30 23:59 UTC, that the Federal Reserve announced a rate cut at the June 2026 FOMC meeting. Leaks and speculation don't count."


---

# 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://limelight-1.gitbook.io/limelight-docs/for-creators/resolution-sources.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.