> For the complete documentation index, see [llms.txt](https://learn.trovemarkets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.trovemarkets.com/trove-x-polymarkets/collectible-index-prediction-markets.md).

# Collectible index prediction markets

Beyond listing Polymarket binaries as perps on Trove, we are also creating **collectible index** markets directly on Polymarket.

These are binary markets like:

* “Pokémon Index > $2,000 by end of December?”
* “CS2 Skins Index > $X by month-end?”
* “Labubu Floor Index > $Y by quarter end?”

### **What “oracle-resolved” means here**

For these markets, the YES/NO outcome is determined by **Trove’s index oracle value** at a **specified resolution timestamp**.

* **YES** if the index is above the threshold at resolution time
* **NO** otherwise

The important part is that the resolution is **mechanical**:

1. The market specifies an **index** (e.g. Pokémon Index)
2. It specifies a **threshold** (e.g. $2,000)
3. It specifies an **exact timestamp** (e.g. Dec 31, 23:59:00 UTC)
4. Trove’s oracle publishes the index value for that timestamp
5. Settlement uses that value as the reference

### **Index oracle characteristics (why it’s usable for resolution)**

A collectible index can’t behave like a single exchange price. So the oracle is designed to output a value that is:

* **Timestampable** (a value tied to a precise time boundary)
* **Reproducible** (methodology is fixed; no discretionary overrides)
* **Robust to thin prints** (index methodology avoids single-trade domination)
* **Auditable** (inputs + calculations are disclosed per index)

> Oracle inputs, index methodology, and the exact timestamp used are shown on the Transparency Dashboard per market.


---

# 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://learn.trovemarkets.com/trove-x-polymarkets/collectible-index-prediction-markets.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.