Oracle composition

Why and how price data points vary

Component	Source	Purpose	Initial Weight	Dynamic Range (Beta)
Mark	Trove user trades	Reflects live sentiment and liquidity	33%	33–50%
Validator	25+ verified external marketplaces	Anchors oracle in real-world sales	33%	25–40%
EMA	Modeled trendline from Trove data	Smooths volatility and refines responsiveness	33%	33–50%

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.

This evolution allows the oracle to adapt naturally as the market becomes more liquid.

---

Oracle revolution

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

Stage	Oracle Behavior	Weight Distribution	Goal
Early	Oracle grounded in external validation; minimal reflexivity.	Validator 50–60%, Mark/EMA ≤25% each	Accuracy & anti-manipulation
Growth	Internal trading deepens; faster mark–oracle convergence.	Validator 35–45%, Mark 30–40%, EMA 25–35%	Responsiveness & efficiency
Mature	Trove achieves continuous, on-chain price discovery.	Validator ≤30%, Mark/EMA 35–50%	Trove leads market pricing

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.