> 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.md). # Pixona Ecosystem ## PIXONA Ecosystem ### One Ecosystem. Three Core Components. The PIXONA ecosystem is built around three connected components: **PIXONA Genesis (V1)**, **MUTAGEN**, and **PIXONA Onchain (V2)**. Each collection has a different purpose, but none of them are designed to operate independently. V1 establishes the foundation of the PIXONA brand and IP. MUTAGEN provides an alternative path through the Evolution Protocol. V2 introduces the fully onchain technology that will support the future of the ecosystem. Together, they create a system where each component contributes to the growth of the others. *** ## The PIXONA Ecosystem ``` PIXONA ECOSYSTEM ┌─────────────────────┐ │ PIXONA GENESIS │ │ V1 │ │ │ │ IP • Brand • │ │ History • Community│ └──────────┬──────────┘ │ Genesis Evolution │ ▼ ┌─────────────────────┐ │ PIXONA ONCHAIN │ │ V2 │ │ │ │ Technology • │ │ Onchain Development │ └──────────▲──────────┘ │ MUTAGEN │ Alternative Evolution │ ┌──────────┴──────────┐ │ │ │ MUTAGEN │ │ │ │ Evolution Catalyst │ │ 2,222 Supply │ └─────────────────────┘ ``` The ecosystem can be understood through three simple roles: **V1 = Foundation** **MUTAGEN = Catalyst** **V2 = Technology** *** ## PIXONA Genesis (V1) ### The Foundation PIXONA Genesis is the original PIXONA NFT collection and the starting point of the ecosystem. V1 represents the history of PIXONA, its original community, its IP, and the foundation upon which everything else is being built. The Genesis Collection will remain an important part of the ecosystem even after the V2 migration. Its role will gradually expand beyond being simply the original NFT collection. V1 will become an important foundation for: * PIXONA IP * Brand expansion * Community * Future collaborations * Ecosystem initiatives * Collectible history V1 represents **where PIXONA came from**. *** ## MUTAGEN ### The Evolution Catalyst MUTAGEN is a separate collection designed specifically to support the Evolution Protocol. It has a permanently fixed supply of **1,111 NFTs**, divided into three variants: | Variant | Name | Supply | | --------- | ------------------ | --------: | | P01 | Community Mutation | 1900 | | P02 | Advanced Mutation | 260 | | P03 | Prime Mutation | 62 | | **Total** | | **2,222** | MUTAGEN provides an alternative way to evolve into PIXONA V2 without burning a Genesis NFT. Instead, the MUTAGEN itself is consumed during the evolution process. Each variant corresponds to a specific V2 batch: **P01 → Common** **P02 → Rare** **P03 → Epic** Once consumed, the MUTAGEN permanently leaves circulation. MUTAGEN therefore acts as the **catalyst between the original PIXONA collection and its fully onchain future**. For the complete MUTAGEN documentation, see the dedicated MUTAGEN section. *** ## PIXONA Onchain (V2) ### The Technological Foundation PIXONA Onchain is the next generation of the PIXONA ecosystem. Unlike the Genesis Collection, V2 is being designed to be **fully onchain**. The purpose of this architecture is to give PIXONA the technical freedom to develop new mechanics and experiences directly around the NFTs. V2 will have a permanent supply of: **3,333 NFTs** The collection will be released through controlled rarity batches, beginning with Common and progressing toward the rarer stages of the collection. V2 is designed to support future development such as: * Dynamic NFT mechanics * Interactive experiences * Onchain games * Character evolution * Trait mechanics * New customization systems * Future ecosystem utilities V2 represents **where PIXONA is going**. *** ## How They Work Together The three components are connected through the Evolution Protocol. A Genesis holder can participate through the traditional **Genesis Evolution Path** by burning the required V1 NFTs. A MUTAGEN holder can participate through the **MUTAGEN Evolution Path** by consuming a compatible MUTAGEN. Both paths lead to the same destination: **PIXONA Onchain (V2).** Neither path can create additional V2 supply. Every evolution fills one of the existing **3,333 V2 slots**. *** ## Different Roles, Same Ecosystem The collections are not designed to compete with each other. They are designed to complement one another. | Component | Role | Supply | | ----------------------- | ------------------------------- | -----------: | | **PIXONA Genesis (V1)** | IP, Brand & Foundation | 3,333 target | | **MUTAGEN** | Evolution Catalyst | 2,222 | | **PIXONA Onchain (V2)** | Technology & Future Development | 3,333 | This separation allows each component to have a clear purpose without making one collection irrelevant. V1 preserves the identity and history of PIXONA. MUTAGEN facilitates evolution. V2 provides the technology needed for the next stage. *** ## A Connected Future The PIXONA ecosystem is not meant to stop at the V2 migration. V2 gives us the technical foundation to continue building, while V1 provides the IP and community foundation needed to grow the brand. MUTAGEN connects the two and creates another way for collectors to participate in the transition. As the ecosystem develops, new utilities, products, mechanics, and experiences can be built around these three components. The exact direction will continue to evolve as development progresses. The important part is that the foundation is being built to support that growth. *** ## The Simple Version If you want to understand the PIXONA ecosystem in three lines: **V1 is where PIXONA came from.** **MUTAGEN helps PIXONA evolve.** **V2 is where PIXONA builds what comes next.** Three components. Different purposes. One ecosystem. --- # 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.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.