> 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/introduction.md). # Introduction ### Introducing PIXONA Onchain (V2) **PIXONA Onchain (V2)** is the next generation of the PIXONA ecosystem and the foundation for everything we want to build next. The original **PIXONA Genesis (V1)** successfully established the collection, community, IP, and brand. However, V1 was not built fully onchain, which limits what we can develop directly around the NFTs. V2 is designed to change that. The goal is to build a **fully onchain PIXONA collection** that gives us the technical freedom to experiment, develop, and create new experiences directly around the NFTs. This means V2 isn't simply another NFT collection. It is the technological foundation for the next chapter of PIXONA. *** ### Built From the Genesis V2 does not replace PIXONA Genesis. Instead, both collections are designed to serve different purposes within the same ecosystem. **PIXONA Genesis (V1)** represents the foundation of the project — its history, IP, brand, and community. **PIXONA Onchain (V2)** represents the technological evolution of PIXONA and provides the foundation for future onchain development. They are not competing collections. They are two parts of the same ecosystem. *** ### A Different Way to Create NFTs One of the biggest differences between V1 and V2 is how V2 NFTs are created. Instead of simply receiving a randomly generated character, eligible holders will be able to access the **PIXONA V2 Designer** and create their own PIXONA using a collection of available traits. The process is designed around: **Evolution → Design → Customize → Deploy** Once the character is finalized, it becomes part of the fully onchain PIXONA V2 collection. This gives holders a more active role in creating their PIXONA rather than simply collecting one. *** ### The Evolution Protocol PIXONA V2 will be introduced through the **Evolution Protocol**. There will be two official ways to evolve into V2: #### Genesis Evolution Holders can burn the required number of PIXONA Genesis (V1) NFTs to unlock a V2 evolution slot. #### MUTAGEN Evolution Holders can alternatively consume a compatible **MUTAGEN** NFT to unlock a V2 evolution slot while preserving their Genesis NFT. Both paths lead to the same destination: **One evolution creates one PIXONA V2.** MUTAGEN does not create additional V2 supply. It simply provides an alternative way to participate in the existing Evolution Protocol. *** ### A Fixed 3,333 Supply PIXONA Onchain (V2) will have a permanent maximum supply of **3,333 NFTs**. The collection will be released progressively through multiple rarity batches: | Rarity | Supply | | --------- | --------: | | Common | 2,413 | | Rare | 600 | | Epic | 220 | | Legendary | 90 | | 1/1 | 10 | | **Total** | **3,333** | Each batch must reach its allocation before the next batch becomes available. This controlled release is designed to preserve the rarity structure and maintain the long-term sustainability of the collection. *** ### Fully Onchain by Design The most important part of V2 is its architecture. By building PIXONA V2 fully onchain, we remove many of the technical limitations associated with the original collection and create a stronger foundation for future development. This opens the door to possibilities such as: * Dynamic NFT mechanics * Interactive experiences * Onchain games * Trait and character mechanics * Evolution systems * New forms of customization * Experimental onchain utilities * Future PIXONA products and experiences These are possibilities enabled by the technology, not promises of specific products. The purpose of building fully onchain is to give PIXONA the freedom to explore them. *** ### One Ecosystem, Multiple Roles The PIXONA ecosystem is built around three primary components: **V1 — The Foundation** The original collection that establishes the PIXONA IP, history, brand, and community. **MUTAGEN — The Catalyst** A fixed collection of **1,111 Evolution Keys** that provides an alternative path into the Evolution Protocol. **V2 — The Onchain Foundation** The fully onchain collection designed to become the technological foundation for future PIXONA development. Together, they form one connected ecosystem. *** ### The Beginning, Not the End PIXONA V2 is not intended to be the final destination of the project. It is the foundation that allows us to build what comes next. As the ecosystem develops, we will continue exploring new utilities, products, mechanics, and experiences that can take advantage of the fully onchain architecture. Once the V2 migration is successfully completed and both the Genesis and Onchain collections reach their respective **3,333 supply targets**, we will announce the next chapter of PIXONA. For now, the mission is simple: **Build the foundation. Evolve PIXONA. Then build on top of it.** --- # 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/introduction.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.