> 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/genesis-collection-v1.md). # Genesis Collection (V1) ### The Beginning of PIXONA The **PIXONA Genesis Collection (V1)** is the original PIXONA NFT collection and the foundation of the entire ecosystem. It represents the first chapter of PIXONA — the collection that established the brand, brought the original community together, and created the foundation for everything that is being built today. V2 is the technological evolution of PIXONA, but V1 will always remain the origin of the ecosystem. *** ## The Foundation of the IP V1 is more than the first PIXONA collection. It represents the beginning of the PIXONA IP and the foundation for future brand expansion. As the ecosystem grows, V1 will continue to play an important role in areas such as: * PIXONA IP * Brand expansion * Community * Collaborations * Merchandise * Future ecosystem initiatives * Historical significance The role of V1 may continue to expand as the PIXONA brand develops. *** ## The V1 Collection The Genesis Collection originally launched with a total supply of: **10,000 PIXONA NFTs** The collection successfully sold out, establishing the first major milestone for the PIXONA ecosystem. Through the project's ongoing buyback-and-burn initiative, the Genesis supply is progressively reduced. The long-term target is: **3,333 PIXONA Genesis NFTs** This target is an important part of the transition toward PIXONA Onchain (V2). *** ## The Road to 3,333 Before the V2 migration begins, PIXONA will continue its planned Genesis buyback-and-burn process. The migration begins once the Genesis Collection reaches the designated: **8,000 V1 supply** At that point, the required pre-migration burn has been completed and the project can move forward with the V2 Evolution Protocol. The buyback-and-burn mechanism is not intended to continue indefinitely. Once V2 migration begins, the V1 buyback-and-burn program will stop, and the treasury will transition toward funding ecosystem development and future initiatives. *** ## Genesis Evolution Once the V2 migration begins, Genesis holders will have the opportunity to participate in the **Genesis Evolution Path**. By burning the required number of V1 NFTs, holders can unlock an evolution slot and create a PIXONA Onchain (V2). The number of Genesis NFTs required depends on the V2 batch being accessed. As the V2 rarity increases, the required Genesis sacrifice also increases. This creates a direct relationship between: **Genesis Scarcity → Evolution Cost → V2 Rarity** Every Genesis NFT used for evolution is permanently removed from circulation. *** ## An Alternative Path Through MUTAGEN Genesis holders are not required to burn their V1 if they have access to a compatible MUTAGEN. The **MUTAGEN Evolution Path** allows collectors to consume a MUTAGEN NFT instead while preserving their Genesis NFT. This gives holders two different ways to participate in V2: #### Genesis Evolution **Burn V1 → Unlock V2** #### MUTAGEN Evolution **Consume MUTAGEN → Preserve V1 → Unlock V2** Both paths create one V2 and remain subject to the same fixed V2 supply. *** ## V1 and V2 Are Not Competitors The launch of V2 does not make V1 obsolete. The two collections are designed to serve different purposes. **V1** IP, brand, history, community, and Genesis identity. **V2** Fully onchain technology, experimentation, and future ecosystem development. V1 represents the foundation. V2 represents the technological future. Both remain connected through the PIXONA ecosystem. *** ## Royalties Following the V2 migration, both collections will contribute to the PIXONA treasury through their respective royalty structures. **PIXONA Genesis (V1): 5% enforced royalties** **PIXONA Onchain (V2): 5% enforced royalties** These royalties provide an ongoing source of funding for the ecosystem. The treasury can be used to support continued development, infrastructure, marketing, brand expansion, future products, and other ecosystem initiatives. The specific treasury allocation will be announced before the V2 migration. *** ## After the Migration Once the V2 migration is successfully completed, V1 will continue to exist as a core part of the PIXONA ecosystem. Its purpose will shift further toward: **IP + Brand + Community + History** while V2 focuses on: **Technology + Onchain Development + Future Utilities** The two collections will continue to work together rather than replacing one another. *** ## The Genesis Legacy Every ecosystem needs an origin. For PIXONA, that origin is V1. It is the collection that started the project, established the community, created the IP, and made the development of the next generation possible. As PIXONA moves toward a fully onchain future, the Genesis Collection remains the foundation from which that future was built. **V1 is where PIXONA began.** **V2 is what we're building toward.** --- # 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/genesis-collection-v1.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.