> For the complete documentation index, see [llms.txt](https://pixonaorg.gitbook.io/pixonaorg-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pixonaorg.gitbook.io/pixonaorg-docs/supply-and-burning.md).

# Supply & Burning

## Treasury Buyback & Burn

The **Treasury Buyback & Burn Program** is designed to reduce the Genesis supply before and during the transition into PIXONA V2.

The program uses treasury funds to acquire PIXONA Genesis NFTs from the market and permanently burn them.

The objective is to achieve the required Genesis supply reduction needed for the V2 migration while maintaining the long-term target of **3,333 Genesis NFTs**.

### Dynamic Migration Target

The final buyback requirement is not based on a fixed V1 supply number.

Instead, the required burn amount will account for the Genesis NFTs that are expected to be permanently removed through the **MUTAGEN Evolution Path**.

MUTAGEN provides an alternative way to access V2 without burning Genesis NFTs directly. However, each MUTAGEN evolution still represents one V2 evolution that would otherwise require participation through the Genesis Evolution Path.

Therefore, the total Genesis reduction required for the migration will be calculated alongside the expected contribution of MUTAGEN.

> **The Treasury Buyback & Burn Program concludes only after the required migration supply has been achieved, taking into account the total Genesis burn reductions introduced by the MUTAGEN collection.**

This creates a more flexible supply model where the final treasury buyback target can adjust according to actual MUTAGEN participation.

***

### Why the Target Is Dynamic

MUTAGEN introduces an alternative evolution path.

If more holders use MUTAGEN to evolve into V2, fewer Genesis NFTs may need to be used through the Genesis Evolution Path.

If fewer MUTAGENs are used, more Genesis NFTs may need to participate in the Genesis Evolution process.

This allows the migration system to adapt to actual community participation instead of relying on a rigid predetermined burn number.

```
MUTAGEN Evolution
        ↓
Genesis NFTs Preserved
        ↓
Less Genesis Burn Required
        ↓
Adjusted Treasury Buyback Target
```

The opposite can also occur:

```
Lower MUTAGEN Participation
        ↓
More Genesis Evolution
        ↓
More Genesis NFTs Burned
        ↓
Lower Additional Treasury Buyback Requirement
```

The treasury therefore only needs to continue buying and burning Genesis NFTs until the required migration reduction has been satisfied.

***

### End of the Buyback Program

Once the required migration supply has been achieved, the Treasury Buyback & Burn Program will conclude.

The treasury can then shift its focus toward supporting the next stage of the ecosystem, including:

* V2 development
* Onchain infrastructure
* Marketing
* Community development
* Future ecosystem initiatives
* New products and utilities

The purpose of the buyback program is therefore not to permanently remove Genesis NFTs indefinitely.

It exists to help prepare the Genesis supply for the transition into the next stage of PIXONA.

***

### The Goal

The long-term Genesis target remains:

**3,333 PIXONA Genesis NFTs**

The path toward that target can come from a combination of:

**Treasury Buyback & Burn**

*

**Genesis Evolution**

*

**MUTAGEN's impact on the Evolution Protocol**

This approach keeps the supply mathematics flexible while maintaining the core objective of the PIXONA ecosystem:

**3,333 Genesis**

**3,333 V2**

**One connected evolution.**


---

# 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://pixonaorg.gitbook.io/pixonaorg-docs/supply-and-burning.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.