> 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/usdpixel-whitepaper/lessons-learned-and-revised-vision.md).

# Lessons Learned & Revised Vision

In 2024, Pixels experienced rapid growth, becoming the top web3 title by daily active users and generating $20 million in revenue. However, we also faced significant challenges:

* Token Inflation: Excessive token emissions led to inflationary pressures.
* Sell Pressure: Many players were extracting value without meaningful reinvestment or contribution back to the ecosystem, negatively impacting the token economy.
* Mis-targeted Rewards: Our reward distribution lacked precision, often rewarding short-term engagement rather than sustainable value creation.

Recognizing these issues, we’ve pivoted strategically toward smarter, data-driven incentives designed to improve our ecosystem's fundamental economics. Key changes include:

* Data-Backed Incentives: Leveraging advanced analytics to precisely target rewards, ensuring tokens flow to users most likely to reinvest and support the ecosystem long-term.
* Liquidity Fees: Implementing heavier withdrawal fees for $PIXEL to discourage extraction and to redistribute fees back to stakers.
* A New Publishing Model: Rolling out a phased, stake-to-vote-and-earn system where players directly influence and benefit from the success of individual games.

Our revised vision extends beyond optimizing a single game - it’s about creating a robust, decentralized growth platform and prioritizing an ecosystem. Pixels is building what we envision as a decentralized AppsFlyer or Applovin for both Web3 and Web2 games, driven by our North-Star metric, RORS. By systematically improving RORS, we ensure every token spent generates sustainable, measurable returns.

In practice, for the ecosystem this means:

* Prioritizing high-quality DAU over mere quantity, focusing on engaged players who genuinely support the ecosystem
* Introducing $vPIXEL, an ERC-20c spend-only token, allowing seamless transactions across partner games without additional fees.
* Reinforcing growth-focused incentives such as referrals and content creation.

And more specifically for Core Pixels this means:

* Gating core features and earnings behind VIP structures to encourage deeper engagement and spending.
* Enhancing core game loops and reintroducing popular social and casual mechanics that initially propelled Pixels’ growth.
* Automatically staking in-game balances of active users, boosted by holding our Farm Land NFT.

These strategic shifts may temporarily affect our user metrics, but they lay the foundation for a fundamentally healthier and more sustainable $PIXEL ecosystem. Our long-term goal remains clear: to build the definitive, decentralized user acquisition and reward platform that empowers both Web3 and Web2 gaming economies.


---

# 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/usdpixel-whitepaper/lessons-learned-and-revised-vision.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.