> 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/evolution-protocol.md). # Evolution Protocol ### The System Behind PIXONA V2 The **Evolution Protocol** is the system that connects PIXONA Genesis (V1), MUTAGEN, and PIXONA Onchain (V2). It is the process through which eligible holders can create a PIXONA V2 while maintaining the permanent **3,333 V2 supply cap**. The protocol has been designed around one simple principle: > **Every evolution creates one V2, and no evolution can create additional supply beyond the 3,333 collection cap.** There are two primary paths into V2: **Genesis Evolution** and **MUTAGEN Evolution**. Both paths ultimately lead to the same destination, but they require different assets to be consumed. *** ## How Evolution Works At its simplest, the process looks like this: ``` EVOLUTION PROTOCOL ┌──────────────────────────┐ │ Holder │ └────────────┬─────────────┘ │ Choose Evolution │ ┌─────────────┴─────────────┐ │ │ ▼ ▼ GENESIS EVOLUTION MUTAGEN EVOLUTION │ │ Burn V1 NFTs Consume MUTAGEN │ │ └─────────────┬─────────────┘ │ ▼ Unlock V2 Slot │ ▼ V2 Designer │ ▼ Create PIXONA V2 │ ▼ Fully Onchain NFT ``` The Evolution Protocol determines which assets can be used, which batch can be accessed, and whether an available V2 slot exists. *** ## Evolution Path 1: Genesis The first path is the original Genesis Evolution mechanism. Eligible holders can use their PIXONA Genesis NFTs to unlock a V2 evolution. The required amount of V1 depends on the V2 batch being accessed. Once the required Genesis NFTs are submitted: **V1 NFTs are burned permanently.** The holder then receives access to the corresponding V2 evolution process. This creates a direct relationship between Genesis scarcity and V2 evolution. #### Genesis Path **PIXONA V1** ↓ **Required V1 NFTs** ↓ **Permanent Burn** ↓ **Evolution Slot** ↓ **V2 Designer** ↓ **PIXONA V2** Burned Genesis NFTs cannot be recovered. *** ## Evolution Path 2: MUTAGEN The second path is through the **MUTAGEN** collection. MUTAGEN provides an alternative way to access V2 without burning the holder's Genesis NFT. Instead, an eligible MUTAGEN is consumed. #### MUTAGEN Path **MUTAGEN** ↓ **Verify Compatible Variant** ↓ **Permanent Consumption** ↓ **Evolution Slot** ↓ **V2 Designer** ↓ **PIXONA V2** Once consumed, the MUTAGEN permanently leaves circulation. It cannot be reused or recovered. *** ## MUTAGEN Batch Access Each MUTAGEN variant corresponds to a specific V2 rarity batch. | MUTAGEN | Mutation | V2 Access | | ------- | ------------------ | --------- | | **P01** | Community Mutation | Common | | **P02** | Advanced Mutation | Rare | | **P03** | Prime Mutation | Epic | This creates a clear relationship between the scarcity of each MUTAGEN variant and the V2 batch it can access. P01 provides access to the first V2 batch. P02 provides access to the second. P03 provides access to the third. Higher V2 batches therefore require access to increasingly limited evolution assets. *** ## One Evolution Means One V2 A fundamental rule of the protocol is: ### 1 Evolution = 1 V2 This applies regardless of which evolution path is used. For example: **Burn V1 → 1 V2** or **Consume MUTAGEN → 1 V2** Neither mechanism can produce multiple V2 NFTs from a single evolution. This protects the collection's fixed supply and keeps the Evolution Protocol predictable. *** ## The 3,333 Supply Protection PIXONA V2 has a permanent supply of: **3,333 NFTs** The Evolution Protocol cannot exceed this number. Every evolution consumes one available V2 slot. Once all 3,333 slots have been filled: **The Evolution Protocol for V2 is complete.** No additional V2 NFTs can be created. This is one of the most important rules of the entire system. *** ## Batch-Based Evolution V2 evolution does not happen as one unrestricted release. The collection is divided into sequential batches. #### Batch 1 **Common — 2,413** #### Batch 2 **Rare — 600** #### Batch 3 **Epic — 220** #### Batch 4 **Legendary — 90** #### Batch 5 **1/1 — 10** The protocol progresses through these batches in order. The next batch cannot begin until the current batch reaches its allocation. This creates a controlled evolution process rather than allowing every rarity to be accessed simultaneously. *** ## V2 Designer Once an eligible evolution has been completed, the holder gains access to the V2 creation process. Through the **PIXONA V2 Designer**, the holder can customize their character using the available V2 traits. The process is designed to be: **Evolution → Design → Customize → Finalize → Deploy** The final PIXONA becomes part of the fully onchain V2 collection. The designer therefore becomes an important part of the evolution experience rather than simply being a separate NFT customization tool. *** ## What Happens to the Assets? The Evolution Protocol permanently consumes the asset used to access V2. #### Genesis Evolution The required V1 NFTs are permanently burned. #### MUTAGEN Evolution The MUTAGEN NFT is permanently consumed. The choice of evolution path therefore has different consequences. A Genesis holder who wants to preserve their V1 may choose to use MUTAGEN instead. A holder without MUTAGEN may participate through the Genesis path if they meet the required conditions. *** ## Evolution and Scarcity The Evolution Protocol is also designed to create natural changes in supply. When Genesis NFTs are used: **V1 supply decreases.** When MUTAGEN is used: **MUTAGEN supply decreases.** When an evolution occurs: **V2 supply increases.** This creates a connected supply relationship between the three components of the ecosystem. ``` V1 Burn ↓ V1 Supply Decreases ↓ V2 Created OR MUTAGEN Consumption ↓ MUTAGEN Supply Decreases ↓ V2 Created ``` The V2 supply, however, can never exceed **3,333**. *** ## After Evolution Once a holder successfully creates their V2, the evolution process is complete. The resulting PIXONA becomes part of the V2 collection and can participate in future utilities and experiences developed around the fully onchain ecosystem. The Evolution Protocol itself is therefore not the final utility. It is the bridge that moves PIXONA from the Genesis era into the onchain era. *** ## The Purpose of the Protocol The Evolution Protocol was designed to accomplish several goals at the same time: * Transition PIXONA from V1 to V2. * Reduce the Genesis supply through meaningful evolution. * Introduce MUTAGEN as an alternative evolution asset. * Maintain the permanent 3,333 V2 supply. * Create controlled rarity-based releases. * Give holders an active role in creating their V2. * Establish a foundation for future onchain development. Most importantly, the system connects all three parts of the ecosystem without making any of them meaningless. **V1 provides the foundation.** **MUTAGEN provides the alternative path.** **The Evolution Protocol connects them.** **V2 becomes the onchain future.** --- # 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/evolution-protocol.md?ask=&goal= ``` `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.