# Rarity Tiers & Functional Differences

| BrewOWL                    | Supply                                             | Visual Traits          | Functional Role                                                                                  |
| -------------------------- | -------------------------------------------------- | ---------------------- | ------------------------------------------------------------------------------------------------ |
| **SSR (Super Super Rare)** | 200 NFTs                                           | Unique visuals         | **Yield Node NFT** — eligible for platform-level revenue sharing                                 |
| **SR (Super Rare)**        | 2,000 NFTs                                         | Unique visuals         | **Yield Node NFT** — eligible for platform-level revenue sharing                                 |
| **R (Rare)**               | 20,000 NFTs                                        | Unique visuals         | **Yield Node NFT** — eligible for platform-level revenue sharing                                 |
| **N (Normal)**             | 50,000 NFTs+ (dynamically scaled with user growth) | Procedurally generated | **Access Pass NFT** — enables entry into Play-to-Earn gameplay; not eligible for revenue sharing |

**📌 Notes:**

* **SSR / SR / R NFTs** are classified as **node-tier assets** — granting holders a proportional share of platform-generated revenues through structured staking mechanics.
* **N (Normal) NFTs** function as **access credentials**, unlocking participation across all Multi-Earn systems, but **do not carry any yield or revenue sharing.**


---

# 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://bre3-official.gitbook.io/bre3-official/core-concepts/markdown/rarity-tiers-and-functional-differences.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.