> 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/batch-and-rarity-system.md).

# Batch & Rarity System

### A Controlled V2 Release

PIXONA V2 will not be released as one complete collection from day one.

Instead, the **3,333 V2 NFTs** will be introduced through a controlled batch system.

Each V2 batch represents a specific rarity level and becomes available according to the Evolution Protocol.

The V2 progression is:

**Common → Rare → Epic → Legendary → 1/1**

The batch system applies specifically to **PIXONA V2**. MUTAGEN is not released through batches.

***

## V2 Rarity Allocation

The permanent V2 supply is divided into five rarity levels:

| Batch       | Rarity    |    Supply | Allocation |
| ----------- | --------- | --------: | ---------: |
| **Batch 1** | Common    |     2,413 |     72.40% |
| **Batch 2** | Rare      |       600 |     18.00% |
| **Batch 3** | Epic      |       220 |      6.60% |
| **Batch 4** | Legendary |        90 |      2.70% |
| **Batch 5** | 1/1       |        10 |      0.30% |
| **Total**   |           | **3,333** |   **100%** |

These allocations represent the permanent maximum for each V2 rarity.

***

## How the V2 Batch System Works

The V2 collection progresses through five defined stages.

#### Batch 1 — Common

**2,413 NFTs**

This is the starting point of the V2 evolution.

Once the Common allocation is completed, the protocol can progress to the next stage.

#### Batch 2 — Rare

**600 NFTs**

The second stage introduces a significantly smaller allocation and higher rarity.

#### Batch 3 — Epic

**220 NFTs**

The third stage continues the progression toward the highest V2 rarities.

#### Batch 4 — Legendary

**90 NFTs**

A highly limited V2 rarity with a significantly smaller allocation.

#### Batch 5 — 1/1

**10 NFTs**

The final and most limited V2 allocation.

***

## Sequential Progression

The V2 batches are designed to progress in order.

```
BATCH 1
COMMON
2,413
   ↓
COMPLETED
   ↓
BATCH 2
RARE
600
   ↓
COMPLETED
   ↓
BATCH 3
EPIC
220
   ↓
COMPLETED
   ↓
BATCH 4
LEGENDARY
90
   ↓
COMPLETED
   ↓
BATCH 5
1/1
10
   ↓
V2 COMPLETE
3,333
```

This creates a controlled progression instead of making every V2 rarity available simultaneously.

***

## Why Use a Batch System?

The batch system gives PIXONA greater control over the V2 migration.

It allows the ecosystem to:

* Introduce V2 progressively.
* Maintain the intended rarity structure.
* Control access to higher rarities.
* Monitor the evolution process.
* Give the community time to experience each stage.
* Prevent higher rarity allocations from being released prematurely.

The goal is to make V2 feel like an actual evolution rather than a single collection launch.

***

## MUTAGEN Variant Access

Although MUTAGEN is not released through batches, its three variants are connected to specific V2 rarity stages.

Each MUTAGEN variant provides access to a particular V2 rarity when used through the Evolution Protocol.

| MUTAGEN | Variant            | V2 Access |
| ------- | ------------------ | --------- |
| **P01** | Community Mutation | Common    |
| **P02** | Advanced Mutation  | Rare      |
| **P03** | Prime Mutation     | Epic      |

This does **not** mean that MUTAGEN is released in batches.

The entire MUTAGEN collection has a fixed supply of 2,222 **NFTs** from the beginning:

| Variant   |    Supply |
| --------- | --------: |
| P01       |      1900 |
| P02       |       260 |
| P03       |        62 |
| **Total** | **2,222** |

The variants simply determine which V2 rarity the MUTAGEN can access when used.

***

## Genesis Access

Genesis holders can also participate in the V2 batches through the **Genesis Evolution Path**.

The required Genesis sacrifice will depend on the V2 rarity being accessed.

The general relationship is:

**Genesis Evolution Requirement → V2 Batch → V2 Rarity**

The specific requirements for each stage will be announced before the corresponding V2 batch becomes available.

***

## One Evolution, One V2

Regardless of the evolution path:

**1 completed evolution = 1 V2**

This applies to both:

**Genesis Evolution**

and

**MUTAGEN Evolution**

The evolution asset used does not change the number of V2 NFTs created.

This is one of the core rules protecting the permanent **3,333 V2 supply**.

***

## Protecting the Rarity Structure

Each V2 rarity has a fixed maximum.

**Common → 2,413**

**Rare → 600**

**Epic → 220**

**Legendary → 90**

**1/1 → 10**

The protocol cannot create additional NFTs beyond these allocations.

This ensures that the rarity structure remains predictable and that the final V2 collection always consists of exactly:

## 3,333 PIXONA V2

***

## When a V2 Batch Is Complete

Once a V2 batch reaches its full allocation, that stage is considered complete.

The Evolution Protocol can then progress to the next V2 batch.

For example:

**2,413 Common V2s created**

→ Common is complete.

Then:

**Rare becomes available.**

The same progression continues until the final 1/1 allocation is completed.

***

## The Complete V2 Structure

When the entire V2 collection is complete:

| Rarity    |    Supply |
| --------- | --------: |
| Common    |     2,413 |
| Rare      |       600 |
| Epic      |       220 |
| Legendary |        90 |
| 1/1       |        10 |
| **Total** | **3,333** |

This supply structure is designed to remain fixed.

***

## The Purpose

The V2 batch system is designed to create a controlled and understandable evolution process.

V2 progresses from its largest allocation toward its rarest pieces:

**Common → Rare → Epic → Legendary → 1/1**

MUTAGEN does not follow this release structure. Instead, its three variants act as **Evolution Keys** that provide access to specific V2 rarity stages.

Together with Genesis Evolution, this creates two paths into one controlled V2 collection.

**V1 provides the Genesis path.**

**MUTAGEN provides the alternative path.**

**The batch system controls V2 progression.**

**3,333 remains the permanent V2 supply.**


---

# 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/batch-and-rarity-system.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.