> For the complete documentation index, see [llms.txt](https://litepaper.pixels.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://litepaper.pixels.xyz/ecosystem-flywheel-and-data-loop.md).

# Ecosystem Flywheel & Data Loop

The Pixels economy is deliberately circular. Each dollar‑worth of $PIXEL that enters the system is pushed through a closed loop that compounds on itself until the Return on Reward Spend (RORS) exceeds 1 and stays there.

$PIXEL staking → UA credits → player spend → revenue share → staker rewards → richer data → smarter targeting → more games → (back to) $PIXEL staking

#### 1. Stake → UA Credits

Players deposit $PIXEL (or 1 : 1‑backed $vPIXEL) into the validator of their choice — in our case a game, not a node. The size of a game’s staking pool instantly converts into an on‑chain UA budget that the studio can spend on targeted, in‑game rewards instead of Facebook or TikTok ads.

#### 2. UA Credits → Revenue

Those rewards pull in new players and re‑engage old ones. When those players spend inside the game, gross revenue accrues on‑chain in the same contract that minted the UA credits, creating a transparent record of spend versus subsidy.

#### 3. Revenue → Staker Rewards

Each game self-determines the rewards it gives to stakers. However, the more fundamentally sound a game becomes and the more, the more competitive it is able to to

#### 4. Staker Rewards → Data

Every purchase, quest, trade, or withdrawal is logged through the Pixels Events API. This generates an expanding first‑party dataset spanning LTV curves, fraud scores, session depth and churn vectors across all games.

#### 5. Data → Smarter Targeting

Our models retrain nightly. Reward budgets are re‑weighted toward cohorts and moments in the funnel that drive the strongest lift in retention, ARPDAU and, ultimately, RORS. Leakage to extractors falls; real players get higher quality incentives.

#### 6. Smarter Targeting → More Games

Because UA efficiency is visible on‑chain, new studios can underwrite an acquisition budget before they write a single line of Solidity. Each launch enlarges the addressable audience, adds fresh behavioural data, and restarts the loop at a higher base.

Why it matters – a flywheel, not a treadmill. The same unit of $PIXEL can cycle through this loop many times: once as stake, again as a player reward, again as revenue share, and finally as a data point that sharpens the next distribution. The result is a compounding ecosystem where capital, users and insight all recycle instead of leak — pushing RORS steadily upward beyond 1.0.

<br>


---

# 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://litepaper.pixels.xyz/ecosystem-flywheel-and-data-loop.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.