# GATA Pixel {% hint style="info" %} Total reward Distributed : **PHOTON, USD**\ Total Epoch Distributed: **0 Epoch**\ \ (*Last updated: 17 May 2026)*\ *For Epoch details* [↗](https://github.com/ABCharlieEth/snapshots/tree/main/GATA%20Pixels) {% endhint %} ## About the collection **Collection name:** [GATA Pixels](https://stargaze.zone/m/cosmos1rusfnupu3wp0txmc8mw3jn88sx9f7vx4j9m3lcvh7dc3fkxvshpsprsx5h)\ **Network:** Cosmos Hub\ **Collection Type:** Standard mint\ **Collection Size**: 1,111\ **Royalties:** 5% \ Symbol: GPs GATA Pixels is a yield-focused NFT collection built by GATA as an experiment in evolving NFTfi beyond speculation. The collection combines yield generation, redemption-based liquidity, and transparency into a single system designed to make NFTs behave more like functional assets rather than static collectables. The collection consists of 1111 NFTs launched on Stargaze, with rarity tiers that directly impact yield performance. Unlike traditional NFT collections where rarity is mostly cosmetic, GATA Pixels introduces functional rarity, where higher-tier NFTs receive increased yield multipliers. ### Purpose The purpose of GATA Pixels is to address three major limitations that have historically prevented NFTfi from scaling sustainably: * Lack of exit liquidity * Undefined or un-measurable yield * Limited transparency and accountability Traditional NFTs rely heavily on secondary market liquidity, meaning holders can only exit if another buyer is willing to purchase the asset. GATA Pixels introduces a redemption system intended to reduce this dependency and create a more structured ownership model. ### Redemption Model Each GATA Pixel can be redeemed at a predefined value relative to mint price. This introduces a structured exit mechanism that allows holders to leave the system without relying entirely on secondary market demand. The redemption floor is designed to strengthen over time through allocations generated by the system itself.
When NFTs are redeemed, they are not removed permanently. Instead, they are recycled back into the market through Stargaze auction mechanisms, creating a continuous loop of ownership, redemption, and redistribution. This creates a model where capital remains active within the ecosystem rather than fully exiting it. ### Yield Structure GATA Pixels targets an average benchmark yield of approximately 15% annually in USD terms, with expected ranges varying between 11% and 165% depending on rarity tier and system performance. Yield generation is supported through treasury allocations and ecosystem strategies managed within the broader GATA infrastructure. The objective is not only to distribute yield, but to make performance measurable and track able over time through transparent reporting.
### Transparency and Allocation Mint proceeds are allocated into multiple system functions to support long-term sustainability: * Long-term yield generation * Short-term yield strategies * Redemption reserves * Operational infrastructure This structure is designed to balance ongoing rewards, liquidity support, and future ecosystem growth. ### A New NFTfi Primitive GATA Pixels combines: * Yield generation * Redemption-based exit liquidity * Transparent reporting * Functional rarity * Recycling mechanics Together, these components form a new ownership model focused on sustainability, flexibility, and measurable participation. Rather than treating NFTs purely as speculative collectibles, GATA Pixels explores how NFTs can evolve into reusable, yield-bearing digital assets with structured liquidity mechanisms. --- # Agent Instructions: 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: ``` GET https://docs.gatahub.zone/g/gatahub/gata-nfts/gata-pixel.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.