# Category Descriptions

### Play-to-Earn Rewards — 25% (250M RUN)

A long-term reward pool for active players.

Includes:

* daily in-app earnings
* milestone rewards
* event payouts
* seasonal competitions
* expansion of future earning mechanics

Ensures sustainable Move-to-Earn incentives over multiple years.

***

### Liquidity & AMM Pools — 20% (200M RUN)

Allocated for liquidity provisioning on:

* Solana AMMs (Raydium, Orca, Meteora, etc.)
* future DEX integrations

Purpose: maintain price stability, low slippage, and healthy trading volume.

***

### Team & Advisors — 10% (100M RUN)

Reserved for the long-term development team and strategic advisors.

Fund usage:

* compensation
* retention
* performance incentives

Distributed with vesting to align interests with long-term growth.

***

### Staking & Governance — 6% (60M RUN)

Tokens dedicated to:

* staking rewards
* governance participation incentives
* long-term holding motivation

Enables users to earn rewards for supporting network health and decision-making.

***

### Marketing & Partnerships — 5% (50M RUN)

Used to grow the Sneakers Go ecosystem.

Includes:

* influencer campaigns
* cross-project collaborations
* brand partnerships
* user acquisition programs
* promotional events

***

### Treasury / Ecosystem Development — 8% (80M RUN)

Strategic reserve for:

* new game modes
* ecosystem expansion
* research and development
* integration grants
* emergency reserves
* future scaling infrastructure

Treasury is not used for daily rewards.

***

### Public Sale / IDO — 24% (240M RUN)

Tokens reserved for public market distribution.

Includes:

* IDO / launchpad rounds
* whitelist allocations
* strategic public offerings

Ensures fair token access and broad distribution.

***

### Airdrop / Community Rewards — 2% (20M RUN)

Dedicated to activating and rewarding the early community.

Includes:

* onboarding rewards
* referral event bonuses
* social quests
* launch airdrops


---

# Agent Instructions: 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:

```
GET https://sneakers-go.gitbook.io/sneakers-go-docs/usdrun-tokenomics-solana/category-descriptions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.