> For the complete documentation index, see [llms.txt](https://mycompany-155.gitbook.io/solnova/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mycompany-155.gitbook.io/solnova/tokenomics/6-tokenomics.md).

# Tokenomics Overview

The SNOVA tokenomics is designed to be sustainable, deflationary, and value-driven, ensuring longevity from the Big Bang through the Brand Invasion Era.

## Core Statements

1. **Total Max Supply:** **2,500,000,000 SNOVA** (2.5 Billion).
2. **Presale:** 250,000,000 SNOVA + 75,000,000 SNOVA (+30% Extra for presale investors).
3. **Farming:** 2,000,000,000 SNOVA (120,000 NFT full farming).
4. **Game:** 125,000,000 SNOVA (Users engagement).
5. **Emission Control:** 120,000 NFTs will be released over 5 Seasons to mine this supply.

***

## Fund Distribution

Transparency is key. Here is how funds are allocated.

### 1. Presale Funds Allocation

*Funds raised from the initial token sale.*

* **50%** - Capitalization (Liquidity)
* **15%** - Marketing
* **15%** - Development
* **10%** - Team
* **10%** - Community

### 2. NFT Sales Allocation

*Income from ongoing NFT sales (Seasons 1-5).*

* **30%** - Operational & Dev Costs
* **20%** - Add to SNOVA Capitalization
* **20%** - Marketing
* **20%** - Team
* **10%** - Community Bonuses

***

## Total Supply Logic (Why 2.2 Billion?)

The Total Emission is not arbitrary. It is calculated backwards from the **Vision**:

> *How much SNOVA do we need to service the system until it is fully populated (120,000 Stars) and ready for the Brands Era?*

We calculated the farming potential of every NFT across all 5 Seasons, assuming optimal play (Shining Up, Satellites).

### SNOVA Global Emission Calculation

| Season                | NFT Count   | Farming Limit | Total SNOVA Added to Emission |
| --------------------- | ----------- | ------------- | ----------------------------- |
| **Presale (Genesis)** | 1,000       | 120 Months    | \~294,317,323                 |
| **Season 1**          | 5,000       | 15 Months     | \~183,948,327                 |
| **Season 2**          | 10,000      | 12 Months     | \~294,317,323                 |
| **Season 3**          | 20,000      | 9 Months      | \~441,475,985                 |
| **Season 4**          | 30,000      | 6 Months      | \~441,475,985                 |
| **Season 5**          | 55,000      | 0 Months      | 0                             |
| **TOTAL**             | **121,000** |               | **\~1,655,534,943**           |

*Note: The remaining supply covers liquidity provisioning, marketing incentives, and ecosystem buffers.*

***

## Deflationary Mechanics

SNOVA is constantly burned or removed from circulation:

1. **Burn to Shine:** The massive cost to upgrade stars.
2. **Ship Customization:** Buying skins.
3. **Brand Era (The Flywheel):** Brands buy SNOVA from the market to pay for campaigns.

> \[!TIP] **The Cycle:** Tokens burned during "Shine Up" or spent on Skins return to the System Reserve. We effectively resell them or burn them to manage price stability.


---

# 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://mycompany-155.gitbook.io/solnova/tokenomics/6-tokenomics.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.