> 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/oracle/oracle-composition.md).

# Oracle composition

<figure><img src="/files/SNybUsGAbayctQelHDHi" alt=""><figcaption></figcaption></figure>

<table data-header-hidden><thead><tr><th width="117.28125"></th><th width="179.09375"></th><th width="195.6328125"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Component</strong></td><td><strong>Source</strong></td><td><strong>Purpose</strong></td><td><strong>Initial Weight</strong></td><td><strong>Dynamic Range (Beta)</strong></td></tr><tr><td><strong>Mark</strong></td><td>Trove user trades</td><td>Reflects live sentiment and liquidity</td><td>33%</td><td>33–50%</td></tr><tr><td><strong>Validator</strong></td><td>25+ verified external marketplaces</td><td>Anchors oracle in real-world sales</td><td>33%</td><td>25–40%</td></tr><tr><td><strong>EMA</strong></td><td>Modeled trendline from Trove data</td><td>Smooths volatility and refines responsiveness</td><td>33%</td><td>33–50%</td></tr></tbody></table>

During Trove Beta, these weights will be actively tested and tuned as market depth improves.\
For example, as trading volume increases and continuous price formation occurs, Mark and EMA may exceed 33%, while Validator weight decreases proportionally.

{% hint style="success" %}
This evolution allows the oracle to adapt naturally as the market becomes more liquid.
{% endhint %}

***

#### Oracle revolution

Trove’s oracle evolves as the platform matures, transitioning from external reliance to internal leadership.

<table data-header-hidden><thead><tr><th></th><th width="249.78515625"></th><th width="211.3203125"></th><th></th></tr></thead><tbody><tr><td><strong>Stage</strong></td><td><strong>Oracle Behavior</strong></td><td><strong>Weight Distribution</strong></td><td><strong>Goal</strong></td></tr><tr><td><strong>Early</strong></td><td>Oracle grounded in external validation; minimal reflexivity.</td><td>Validator 50–60%, Mark/EMA ≤25% each</td><td>Accuracy &#x26; anti-manipulation</td></tr><tr><td><strong>Growth</strong></td><td>Internal trading deepens; faster mark–oracle convergence.</td><td>Validator 35–45%, Mark 30–40%, EMA 25–35%</td><td>Responsiveness &#x26; efficiency</td></tr><tr><td><strong>Mature</strong></td><td>Trove achieves continuous, on-chain price discovery.</td><td>Validator ≤30%, Mark/EMA 35–50%</td><td>Trove leads market pricing</td></tr></tbody></table>

This lifecycle ensures Trove doesn’t dictate price prematurely — it earns trust through transparency and liquidity. The oracle evolves from being an observer of markets to becoming their reference standard.


---

# 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/oracle/oracle-composition.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.