> 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/pixona-ecosystem/mutagen.md).

# MUTAGEN

## MUTAGEN

### The Catalyst of Evolution

**MUTAGEN** is a core component of the PIXONA ecosystem and an alternative path into the Evolution Protocol.

It was created to help bridge the transition between the original **PIXONA Genesis (V1)** and the fully onchain **PIXONA V2**.

Instead of burning a Genesis NFT to participate in the evolution process, eligible holders can consume a compatible MUTAGEN and preserve their V1 while unlocking access to create a V2.

MUTAGEN is not designed to replace Genesis evolution.

It is designed to provide another way to evolve.

***

## 1,111 Fixed Supply

MUTAGEN has a permanently fixed supply of **1,111 NFTs**.

The collection consists of three different mutation formulas:

| Variant   | Name               | Supply | V2 Batch |
| --------- | ------------------ | -----: | -------- |
| **P01**   | Community Mutation |   1900 | Common   |
| **P02**   | Advanced Mutation  |    260 | Rare     |
| **P03**   | Prime Mutation     |     62 | Epic     |
| **Total** |                    |  2,222 |          |

Each variant has a specific role within the Evolution Protocol.

No additional MUTAGEN variants or supply will be added.

***

## How MUTAGEN Works

MUTAGEN acts as a **one-time Evolution Key**.

When a compatible MUTAGEN is activated through the Evolution Protocol:

**MUTAGEN → Consumed → Evolution Unlocked → V2 Created**

The MUTAGEN is permanently consumed after the evolution is completed.

It cannot be reused, recovered, or activated again.

This means the circulating supply of MUTAGEN naturally decreases as more holders participate in the evolution process.

***

## Preserving Your Genesis

One of the primary benefits of MUTAGEN is that it allows holders to participate in V2 without sacrificing their Genesis NFT.

For example:

**Genesis Evolution**

Burn required V1 NFTs\
↓\
Unlock V2

**MUTAGEN Evolution**

Consume compatible MUTAGEN\
↓\
Keep V1\
↓\
Unlock V2

Both methods ultimately create one PIXONA V2.

The difference is what the holder chooses to sacrifice.

***

## Batch Access

Each MUTAGEN variant is connected to a specific V2 rarity batch.

#### P01 — Community Mutation

Unlocks the **Common Batch**.

#### P02 — Advanced Mutation

Unlocks the **Rare Batch**.

#### P03 — Prime Mutation

Unlocks the **Epic Batch**.

The batch system remains sequential.

A higher batch cannot be accessed until the previous batch has reached its full allocation.

This keeps the V2 release controlled and protects the intended rarity structure.

***

## MUTAGEN Does Not Increase V2 Supply

An important part of the Evolution Protocol is that MUTAGEN does not create additional V2 NFTs.

PIXONA V2 has a permanent maximum supply of:

**3,333 NFTs**

Whether a V2 is created through Genesis burning or MUTAGEN consumption, it fills one of those existing evolution slots.

For example:

```
Genesis Evolution
       OR
MUTAGEN Evolution
       ↓
One Evolution
       ↓
One V2
```

There is no additional V2 supply created through MUTAGEN.

***

## Why MUTAGEN Exists

MUTAGEN serves several purposes within the PIXONA ecosystem.

First, it provides collectors with another way to participate in the V2 migration.

Second, it allows Genesis holders to preserve their original NFTs while still evolving into V2.

Third, it introduces a finite protocol asset that becomes progressively scarcer as it is consumed.

Finally, MUTAGEN helps introduce the PIXONA V2 vision to a broader audience and creates a foundation of participation around V2 before and during its migration.

It is both an evolution mechanism and an important part of the ecosystem's transition toward fully onchain technology.

***

## A Collection With a Purpose

MUTAGEN was not created simply as another collectible collection.

Every MUTAGEN has a defined purpose within PIXONA.

It exists to facilitate evolution.

Once that purpose has been fulfilled, it is permanently consumed.

This makes MUTAGEN fundamentally different from a traditional NFT collection where the supply is expected to remain unchanged.

Over time, the collection naturally becomes smaller as more holders evolve.

***

## Learn More

The V2 documentation only provides a brief overview of MUTAGEN and its role within the Evolution Protocol.

For the complete details regarding:

* MUTAGEN variants
* Evolution Keys
* Consumption mechanics
* Benefits
* Supply allocation
* Individual mutation formulas
* Future utilities
* MUTAGEN terms

Please refer to the dedicated **MUTAGEN Documentation**.

**MUTAGEN is the catalyst.**

**Evolution is the process.**

**V2 is the destination.**


---

# 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/pixona-ecosystem/mutagen.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.
