> 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/why-v2.md). # Why V2? ### Why Are We Building PIXONA V2? PIXONA Genesis (V1) successfully gave PIXONA its foundation. It launched the collection, brought the community together, established the brand, and created the first chapter of the PIXONA ecosystem. But as we started thinking about what PIXONA could become, we realized that the original collection has technical limitations that make certain ideas difficult or impossible to build. That's where V2 comes in. **PIXONA V2 is not being created because we simply want another NFT collection. We are building V2 because we want to remove the technical limitations that prevent us from building bigger things.** *** ## The Limitations of V1 The Genesis Collection was built to establish PIXONA as an NFT project and bring the original vision to life. However, V1 was not designed as a fully onchain system. Because of that, the collection has limitations when it comes to building advanced mechanics directly around the NFTs. As PIXONA continues to grow, these limitations become more important. We don't want the technology behind the original collection to determine how far the ecosystem can go. *** ## Why Fully Onchain? V2 is being designed from the ground up with a fully onchain architecture. This gives the NFT itself a much stronger foundation for future development. Instead of treating the NFT as a static image with technology built around it, we want the NFT to become part of the technology. That creates significantly more room for experimentation. With a fully onchain foundation, we can explore things such as: * Dynamic NFT mechanics * Onchain games * Interactive experiences * Character evolution * Trait manipulation * Customization systems * Onchain applications * New ecosystem mechanics * Future utilities we haven't even designed yet The goal is not to promise every one of these ideas. The goal is to make sure **we have the technical freedom to build them if they make sense for PIXONA.** *** ## V2 Is More Than a New Collection A common misconception is that V2 is simply a second PIXONA collection. That's not how we're approaching it. V2 is intended to become the **technological foundation of the PIXONA ecosystem**. The collection itself is important, but the technology behind it is what makes V2 different. We want developers to be able to build directly around the NFTs and create experiences that would not be possible with the original Genesis architecture. This is why taking the time to build the foundation correctly matters more than rushing V2 to market. *** ## Giving Holders More Control V2 also changes the way holders participate in creating their NFTs. Through the **PIXONA V2 Designer**, eligible holders will be able to build their own PIXONA using available official traits. Instead of simply receiving a predetermined character, holders become part of the creation process. They can select the available components, customize their character, and ultimately deploy their PIXONA fully onchain. This makes the relationship between the holder and the NFT more interactive. *** ## V1 Still Matters Building V2 does not mean abandoning V1. In fact, V1 remains an important part of the PIXONA ecosystem. **V1 becomes the foundation of the IP, brand, history, and community.** **V2 becomes the foundation of the technology and future onchain development.** The two collections are designed to work together. V1 represents where PIXONA came from. V2 represents where PIXONA can go. *** ## Built for the Long Term We could have simply launched another collection and called it V2. But that would defeat the purpose. The reason we're taking the time to develop V2 properly is because we want it to support years of future development rather than becoming another short-term NFT release. The technology needs to be strong enough to support whatever comes next. The ecosystem needs to be flexible enough to evolve. And the supply needs to remain controlled so that the long-term structure of PIXONA is protected. *** ## The Bigger Picture The long-term structure of PIXONA is built around three connected components: **PIXONA Genesis (V1)**\ The foundation of the IP, brand, history, and community. **MUTAGEN**\ The catalyst that provides an alternative path into the Evolution Protocol while helping introduce more collectors to the next generation of PIXONA. **PIXONA Onchain (V2)**\ The fully onchain technological foundation for future PIXONA development. Each component has a different purpose. Together, they create the foundation for the ecosystem we want to build. *** ## The Goal The goal of V2 has never been simply to create another NFT collection. The goal is to build a foundation that gives PIXONA room to grow. We want to be able to experiment. We want to be able to build. We want to be able to create things that weren't possible with V1. And most importantly, we want the technology to stop being the limitation. **V2 is the foundation.** **What we build on top of it 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/why-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.