> 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/staking-ecosystem-and-token-mechanics/usdvpixel-erc20c.md).

# $vPIXEL (ERC20c)

Traditional fungible tokens can be withdrawn and market‑sold instantly, creating constant sell pressure the moment rewards hit a player’s wallet. To curb extraction without throttling legitimate in‑game spend, we are introducing **$vPIXEL**: a spend‑ and stake‑only apptoken, backed 1 : 1 by $PIXEL and implemented with **ERC‑20c** transfer logic.

### How the Flow Works

1. **Earn $PIXEL** — A player earns Pixel through gameplay or any staking pool
2. **Withdrawal Choice** — When the player wants liquidity they may:
   * **Withdraw $PIXEL**  → pay the **Farmer Fee** 
   * **Withdraw $vPIXEL**  → *0 % fee*, but the token is **non‑tradable** on CEX/DEX.
3. **Spend or Stake $vPIXEL**
   * In‑game purchases across Core Pixels, partner titles, and future apps.
   * Re‑stake for full APR; $vPIXEL counts 1‑for‑1 toward staking power.
4. **Burn‑to‑Unlock Logic** — Every $vPIXEL that is *spent* triggers the permanent unlock of the backing $PIXEL inside the Tokenmaster pool. Studios can recycle those unlocked tokens for UA rewards or treasury operations.

### Why Players Choose $vPIXEL

| Benefit              | $PIXEL | $vPIXEL |
| -------------------- | ------ | ------- |
| Withdrawal fee       | Yes    | No      |
| Tradable on CEX/DEX  | Yes    | **No**  |
| In‑game spend        | Yes    | Yes     |
| Eligible for staking | Yes    | **Yes** |

Players who intend to stay in the ecosystem—spending, staking, or hopping between partner games—have no reason to incur the Farmer Fee.

### Why Studios Care

* **Lower Net Emissions** — Spend‑only tokens recycle value instead of hitting open‑market liquidity.
* **Programmable Controls** — ERC‑20c gates can add task‑gated unlocks or time‑locks if needed.
* **Seamless Integration** — No new contract work; partner games call the same SDK used for $PIXEL.

### Roll‑out Timeline

| Milestone               | Target Date   | Notes                                      |
| ----------------------- | ------------- | ------------------------------------------ |
| Tokenmaster pool seeded | **May 2025**  | Internal audit complete                    |
| In‑game withdrawal UI   | **June 2025** | Fee slider + $vPIXEL option                |
| Farmer Fee on‑chain     | **June 2025** | Initially 20–50 %, governance‑adjustable   |
| Partner‑game support    | **Q3 2025**   | Runiverse + two unannounced titles         |
| Creator drop pools      | **Q4 2025**   | Promotional $vPIXEL for referral campaigns |

$ vPIXEL is a practical demonstration of how app‑level programmability can realign token flows toward retention and spend while preserving full transparency. By giving players a friction‑free alternative to market withdrawals, we expect a measurable reduction in net sell pressure and a corresponding uplift in **RORS** once the mechanism is live.


---

# 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/staking-ecosystem-and-token-mechanics/usdvpixel-erc20c.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.