> 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/v2-technology.md). # V2 Technology ### Built Onchain From the Ground Up PIXONA V2 is being designed around one core idea: **the NFT itself should be the foundation of the technology.** Unlike the Genesis Collection, V2 is being developed as a **fully onchain NFT collection**, giving PIXONA greater flexibility to build new mechanics, experiences, and utilities directly around the characters. The goal is not simply to put the artwork onchain. The goal is to build a collection that can **use onchain technology as part of its core identity.** *** ## Fully Onchain The V2 architecture is designed to keep the essential components of the NFT onchain. This includes the elements required for the PIXONA character and its traits to exist independently within the blockchain environment. The objective is to reduce reliance on external hosting and create a stronger technical foundation for future development. In simple terms: **The character isn't just stored somewhere offchain.** **The character is built around the blockchain itself.** *** ## V2 Designer One of the main systems being developed for V2 is the **PIXONA V2 Designer**. The Designer will allow eligible holders to participate in creating their own PIXONA character. The general process is: ``` Evolution ↓ Access V2 Designer ↓ Select Traits ↓ Customize PIXONA ↓ Finalize Character ↓ Deploy Onchain ``` This makes the holder part of the creation process rather than simply receiving a randomly generated NFT. The final character becomes the holder's PIXONA V2. *** ## Onchain Traits V2 is being designed with an onchain trait system that can support the collection's customization mechanics. Traits can include elements such as: * Character * Expression * Clothing * Accessories * Hair * Background * Special traits The exact trait structure will be finalized during development. The objective is to make the trait system flexible enough to support future V2 mechanics without requiring the entire collection to be rebuilt. *** ## Evolution as a Technical Process The Evolution Protocol is not simply a minting system. It connects the V1 Genesis Collection and MUTAGEN directly to the V2 technology. There are two primary evolution paths: #### Genesis Evolution **Burn V1 → Unlock V2** #### MUTAGEN Evolution **Consume MUTAGEN → Unlock V2** After the required asset has been permanently consumed, the holder can access the V2 creation process. This creates a direct connection between the ecosystem's assets and the onchain V2 infrastructure. *** ## Onchain Character Creation The V2 Designer is intended to make character creation an interactive part of the ecosystem. Instead of generating every V2 entirely beforehand, the system can allow holders to determine aspects of their character during the evolution process. This provides greater flexibility for future mechanics. The long-term goal is to make the PIXONA character more than a static image. It becomes an **onchain identity that can potentially interact with future PIXONA systems.** *** ## Built for Future Development The reason PIXONA is moving toward fully onchain technology is to create room for experimentation. The V2 infrastructure can potentially support future systems such as: * Dynamic NFTs * Interactive characters * Onchain games * Trait evolution * Character progression * Customization mechanics * Onchain experiences * Ecosystem utilities These are potential directions rather than guaranteed features. The important part is that the V2 architecture is being designed to **make these possibilities technically achievable.** *** ## V2 and the Ecosystem V2 does not exist separately from the rest of PIXONA. The technology connects directly with the other ecosystem components. **PIXONA Genesis** Provides the original IP, history, and community foundation. **MUTAGEN** Provides an alternative Evolution Key and helps connect collectors to the V2 migration. **PIXONA V2** Provides the fully onchain technology and foundation for future development. Together: ``` PIXONA GENESIS Foundation │ │ Genesis Evolution ▼ EVOLUTION PROTOCOL ▲ │ MUTAGEN Evolution │ MUTAGEN Catalyst │ ▼ PIXONA V2 Onchain Technology ``` *** ## Technology Before Utility The priority is to build the underlying technology correctly before adding unnecessary features. The V2 infrastructure needs to be stable, secure, and functional before the ecosystem begins expanding into more advanced utilities. This means some planned features may evolve during development. The technology will come first. Utilities and experiences will be built on top of that foundation. *** ## The Long-Term Goal PIXONA V2 is being built to become the technological foundation of the next generation of the ecosystem. The objective is to move from: **Static NFT → Onchain Character** and eventually from: **Onchain Character → Interactive Ecosystem** The final direction will depend on development, community feedback, and what can realistically be built. For now, the priority is simple: **Build V2 fully onchain.** **Make the creation process meaningful.** **Create a strong technical foundation.** **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/v2-technology.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.