> 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/evolution-timeline.md). # Evolution Timeline ### From Genesis to Onchain The PIXONA Evolution Protocol is designed to move the ecosystem through a controlled transition from **Genesis (V1)** to **Onchain (V2)**. The process is not intended to happen all at once. Each stage has a specific purpose, allowing the team to prepare the ecosystem, establish the necessary foundation, and gradually open the V2 collection. The timeline below represents the current planned structure and may be adjusted as development progresses. *** ## Phase 1 — Genesis Foundation #### PIXONA Genesis (V1) The Genesis Collection establishes the foundation of PIXONA. V1 represents: * The original PIXONA IP * The brand * The community * The project's history * The foundation for future development The Genesis collection originally launched with **10,000 NFTs**. The long-term target for the Genesis collection is: **3,333 NFTs** *** ## Phase 2 — MUTAGEN Introduction MUTAGEN introduces an alternative path into the Evolution Protocol. The collection has a fixed supply of: **2,222 MUTAGEN NFTs** Divided into: | Variant | Name | Supply | | --------- | ------------------ | --------: | | P01 | Community Mutation | 1900 | | P02 | Advanced Mutation | 260 | | P03 | Prime Mutation | 62 | | **Total** | | **2,222** | MUTAGEN allows eligible holders to access V2 without burning their Genesis NFT. Instead, the MUTAGEN is consumed during the evolution process. This stage also serves as an early introduction to the V2 concept and helps establish a foundation of community participation before the full migration. *** ## Phase 3 — V2 Development During this stage, the technical foundation of PIXONA V2 is developed. The primary objective is to build the V2 collection as a **fully onchain system**. This includes developing the infrastructure required for: * V2 minting and evolution * Onchain storage * Character generation * V2 Designer * Trait systems * Batch releases * Evolution mechanics * Supply tracking The goal is to make sure the core technology is functional before opening the V2 migration. *** ## Phase 4 — V2 Migration Begins Once the necessary development and preparation are complete, the V2 migration officially begins. At this point: **The Genesis buyback-and-burn program stops.** The treasury will no longer be allocated toward the pre-migration V1 buyback-and-burn initiative. Instead, the treasury transitions toward supporting: * Development * Infrastructure * Marketing * Ecosystem growth * Future products * New utilities The exact treasury allocation will be announced before the V2 migration. *** ## Phase 5 — Batch 1 ### Common The first V2 batch becomes available. **Supply: 2,413** Eligible holders can begin evolving into the first V2 rarity through either: **Genesis Evolution** or **MUTAGEN P01** P01, known as **Community Mutation**, provides access to the Common batch. Once the Common allocation is filled, Batch 1 closes. *** ## Phase 6 — Batch 2 ### Rare The second V2 batch opens. **Supply: 600** Access is available through the applicable evolution requirements and: **MUTAGEN P02 — Advanced Mutation** The Rare batch introduces a more limited V2 rarity and a smaller overall allocation. Once the allocation is filled, the protocol moves forward. *** ## Phase 7 — Batch 3 ### Epic The third V2 batch opens. **Supply: 220** Access is available through the applicable evolution requirements and: **MUTAGEN P03 — Prime Mutation** P03 is the rarest MUTAGEN variant and provides access to the Epic stage. Once the Epic allocation is filled, the protocol progresses toward the final rarity stages. *** ## Phase 8 — Legendary ### Batch 4 The Legendary batch becomes available. **Supply: 90** This stage represents one of the most limited V2 rarity tiers. The Evolution Protocol continues until the full Legendary allocation has been reached. *** ## Phase 9 — 1/1 ### Batch 5 The final V2 rarity stage consists of: **10 unique 1/1 NFTs** These represent the most limited pieces within the V2 collection. Once all 10 have been created, every V2 rarity allocation will have been completed. *** ## Phase 10 — V2 Reaches 3,333 Once every batch has been completed: | Rarity | Supply | | --------- | --------: | | Common | 2,413 | | Rare | 600 | | Epic | 220 | | Legendary | 90 | | 1/1 | 10 | | **Total** | **3,333** | The V2 Evolution Protocol reaches its permanent supply limit. No additional PIXONA V2 NFTs can be created beyond the 3,333 allocation. *** ## Phase 11 — The Next Chapter Reaching the 3,333 V2 supply is not the end of PIXONA. It marks the completion of the initial evolution and migration phase. At this point, both sides of the ecosystem will have reached their intended structure: **PIXONA Genesis — 3,333** **PIXONA Onchain — 3,333** MUTAGEN will have fulfilled its role as an Evolution Catalyst as its supply is consumed through the protocol. Once the V2 launch is successfully completed, the team will announce the next direction for the PIXONA ecosystem. This is where future utilities, products, experiences, and onchain developments can begin taking shape. *** ## The Complete Journey The entire process can be summarized as: ``` GENESIS 10,000 V1 ↓ BUYBACK & BURN ↓ 8,000 V1 ↓ MUTAGEN INTRODUCTION 2,222 Evolution Keys ↓ V2 DEVELOPMENT Fully Onchain Foundation ↓ MIGRATION BEGINS ↓ BATCH 1 Common — 2,413 ↓ BATCH 2 Rare — 600 ↓ BATCH 3 Epic — 220 ↓ BATCH 4 Legendary — 90 ↓ BATCH 5 1/1 — 10 ↓ V2 COMPLETE 3,333 PIXONA ↓ NEXT CHAPTER ``` *** ## A Controlled Evolution The Evolution Protocol is designed to move PIXONA forward without rushing the process. Every stage has a purpose. **V1 establishes the foundation.** **The buyback-and-burn reduces the Genesis supply.** **MUTAGEN introduces an alternative evolution path.** **V2 introduces the fully onchain technology.** **The batch system controls the release.** **3,333 V2 marks the completion of the initial evolution.** And after that, PIXONA moves into its next chapter. **The migration is the beginning of the onchain era, not the end of the project.** --- # 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/evolution-timeline.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.