# Asset Universe Rules

Rebellion maintains a curated, dynamic asset pool to ensure fairness, liquidity, and data integrity across all leagues.

The asset pool is **updated weekly** and includes:

* **Top 100 Cryptocurrencies** by market cap & trading volume
* **Top 200 US & Global Stocks**, selected for liquidity and sector diversity
* **Most Traded Bond ETFs** representing major government and corporate debt
* **Liquid Commodities** via ETF proxies (e.g., gold, silver, oil)

#### Asset Filters

Only assets that meet the following criteria are eligible for selection:

* **Minimum 30-day trading volume** to ensure liquidity
* **Reliable pricing data** via decentralized or trusted oracles (e.g., Chainlink)
* **Sufficient historical performance data** for modeling and scoring accuracy

**Blacklist Criteria**

To preserve the integrity of gameplay and prevent manipulation:

* Illiquid or thinly traded assets
* Low-float or high-volatility microcap stocks
* Memecoins and speculative tokens (except in dedicated *Meme Leagues*)

These are excluded from standard league formats.

**MVP Asset Universe (Day One)**

* **Top 25 Crypto Assets** by market cap (BTC, ETH, SOL, etc.)
* **Top 25 U.S. Equities** from NASDAQ + NYSE (AAPL, TSLA, NVDA, etc.)

These 50 assets cover >70% of typical retail exposure and ensure:

* Reliable price oracles (via Chainlink & TradFi APIs)
* Manageable licensing cost
* Low latency performance data

Additional assets will be added post-MVP based on user demand and data partnerships.


---

# 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://rebellion.gitbook.io/rebellion/platform/asset-universe-rules.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.