> 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/onchain-collection-v2.md). # Onchain Collection (V2) ### The Next Generation of PIXONA **PIXONA Onchain (V2)** is the next generation of the PIXONA ecosystem and the technological foundation for everything we want to build moving forward. Unlike the original Genesis Collection, V2 is being designed as a **fully onchain NFT collection**. The purpose is simple: remove technical limitations and give PIXONA the freedom to build new mechanics, experiences, and utilities directly around the NFT. V2 is not simply another collection. It is the foundation for the next chapter of PIXONA. *** ## Fixed Supply PIXONA V2 will have a permanent supply of: ### 3,333 NFTs The collection will be divided into five rarity categories: | Rarity | Supply | Allocation | | ------------- | --------: | ---------: | | **Common** | 2,413 | 72.40% | | **Rare** | 600 | 18.00% | | **Epic** | 220 | 6.60% | | **Legendary** | 90 | 2.70% | | **1/1** | 10 | 0.30% | | **Total** | **3,333** | **100%** | The supply is permanently capped at 3,333. No additional V2 NFTs will be created beyond this allocation. *** ## A Controlled Release V2 will not be released all at once. The collection will be introduced through a sequential **batch system**. The release order is: **Batch 1 — Common** ↓ **Batch 2 — Rare** ↓ **Batch 3 — Epic** ↓ **Batch 4 — Legendary** ↓ **Batch 5 — 1/1** The next batch will only become available once the previous batch has reached its full allocation. This structure gives the ecosystem a controlled progression and helps preserve the intended rarity distribution. *** ## Fully Onchain The defining feature of V2 is its fully onchain architecture. The objective is to place the NFT itself at the center of the technology rather than relying on the same limitations of the original Genesis architecture. This creates the foundation for future systems that can interact directly with the NFT. Potential areas of development include: * Dynamic NFT mechanics * Interactive experiences * Onchain games * Character evolution * Trait manipulation * Onchain customization * Experimental mechanics * Future ecosystem utilities These are possibilities enabled by the technology and should not be interpreted as guaranteed products. The purpose of building fully onchain is to give PIXONA the freedom to explore them. *** ## The PIXONA V2 Designer One of the core features planned for V2 is the **PIXONA V2 Designer**. Eligible holders will be able to create their own PIXONA character using the official V2 trait system. The general process is: ``` Evolution ↓ Access V2 Designer ↓ Choose Traits ↓ Customize PIXONA ↓ Finalize Character ↓ Deploy Fully Onchain ``` This makes the creation process more interactive and gives holders a role in shaping their own V2. Instead of simply receiving a predetermined character, holders participate in creating the NFT itself. *** ## Two Ways to Enter V2 V2 can be accessed through two official evolution paths. #### Genesis Evolution Burn the required PIXONA Genesis (V1) NFTs to unlock an evolution slot. #### MUTAGEN Evolution Consume the appropriate MUTAGEN to unlock an evolution slot while preserving the Genesis NFT. Both methods ultimately produce: **One PIXONA V2** Neither method can increase the permanent V2 supply beyond 3,333. *** ## Built From V1 V2 is an evolution of the original PIXONA ecosystem. The goal is not to abandon the Genesis Collection but to build upon everything that V1 established. V1 provides: **IP + Brand + History + Community** V2 provides: **Technology + Onchain Development + Future Utilities** MUTAGEN connects the two through the Evolution Protocol. Together, they form one ecosystem. *** ## Royalties and Treasury PIXONA V2 will have **5% enforced royalties**. These royalties will contribute to the PIXONA treasury and provide an ongoing source of funding for ecosystem development. Treasury funds may support areas such as: * Development * Infrastructure * Marketing * Brand expansion * New products * Ecosystem initiatives * Future onchain experiences The final treasury allocation will be announced before the V2 migration. The objective is to create a sustainable source of funding for continued development rather than relying on constant external fundraising. *** ## More Than an NFT The long-term purpose of PIXONA V2 extends beyond the collection itself. The fully onchain architecture gives the team a foundation to experiment and build without being restricted by the technical limitations of V1. The collection is the starting point. The technology is what allows the ecosystem to grow beyond it. As development continues, new utilities, products, mechanics, and experiences can be built around the V2 infrastructure. *** ## The Future of PIXONA PIXONA V2 represents the transition from an NFT collection into a more flexible onchain ecosystem. V1 established the foundation. MUTAGEN facilitates evolution. V2 provides the technology. Once the V2 migration is successfully completed and the collection reaches its permanent **3,333 supply**, the next chapter of PIXONA will begin. **V2 is not the final destination.** **It is the foundation for what comes next.** --- # 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/onchain-collection-v2.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.