> For the complete documentation index, see [llms.txt](https://the-cleanupcentr.gitbook.io/the-cleanupcentr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://the-cleanupcentr.gitbook.io/the-cleanupcentr/documentation/burning-system.md). # πŸ”₯ Burning System #### *How Incinerators Convert NFTs into CINDER Energy* Burning is the foundational mechanic of **The CleanupCentr**.\ It is the process that transforms NFTs into **CINDER**, the energy required to operate farms, tools, and the entire gameplay economy. This page explains the full burning workflow, requirements, outputs, and economic effects. *** ## 🏭 **1. The Incinerator β€” Required for All Burns** Burning **cannot** happen without an **Incinerator NFT**. To burn any NFT, the player must: 1. **Own an Incinerator NFT** 2. **Stake the Incinerator** to the CleanupCentr contract 3. **Have TRASH token** (fuel) 4. **Select a burnable NFT** 5. Confirm the burn β†’ receive CINDER The Incinerator is the gateway to the energy economy. *** ## ♻️ **2. What Happens During a Burn?** When a burn is executed: #### πŸ”₯ **1. The selected NFT is permanently destroyed** The NFT is removed from circulation forever. #### πŸ—‘οΈ **2. TRASH fuel is consumed** TRASH regulates burns and prevents unlimited CINDER generation. #### ⚑ **3. CINDER is created** The contract calculates how much CINDER to issue based on: * NFT category * Burn rules * System configuration #### πŸ“¦ **4. Burn metadata is recorded** This includes: * Burner account * Asset ID * CINDER amount * Timestamp Important for transparency and future systems. *** ## πŸ”‹ **3. Why Burning Exists** Burning drives the entire CleanupCentr economy by: * Removing NFTs from circulation * Generating CINDER (energy) * Creating demand for TRASH fuel * Feeding the farming system * Balancing supply & demand * Supporting long-term sustainability Without burning β†’ no energy β†’ no farming β†’ no TOMATOE. Burning is the **engine** of the gameplay loop. *** ## πŸ—‘οΈ **4. TRASH β€” The Fuel for Burning** Every burn requires **TRASH**. TRASH gives the burn system: #### βœ” Cost Burning isn’t free and reflects resource usage. #### βœ” Balance High TRASH prices slow burning; low prices accelerate it. #### βœ” Circularity TRASH connects burning β†’ CINDER β†’ farming β†’ pack sales β†’ more burning. #### βœ” Governance alignment TRASH is also the governance-aligned token. Burns will automatically stop if a player has insufficient TRASH. *** ## πŸ”₯ **5. Burnable NFTs** Depending on ecosystem configuration, burnable NFTs may include: * Incinerator-compatible items * Utility NFTs * External project NFTs (future) * CleanupCentr items from packs * Seasonal burn events * Farming materials Only approved templates are burnable. Burning unsafe or restricted templates is prevented by the contract. *** ## ⚑ **6. CINDER Output β€” The Energy Token** CINDER is the **reward** for burning. CINDER is used to: * Load energy into Farms * Operate tools (watering, harvesting) * Activate farming cycles * Power future utilities and modules CINDER is **pure utility**, not printed freely, and only created through **burning**. This prevents inflation and ensures all energy is backed by real economic action. *** ## πŸ”‹ **7. Loading CINDER Requires Simple Cores** Burning creates CINDER, but to *use* CINDER, players must load it into a farm. Loading requires: * CINDER (generated from burns) * A **Simple Core** NFT (one-time consumption) This adds an additional layer of: * NFT sinks * Energy regulation * Economy balance * Crafting utility * Market activity Burning + Simple Core = full energy cycle activation. *** ## πŸ” **8. Burning and Market Interaction** Burn volume affects the ecosystem: #### If burning increases: * More CINDER enters economy * Farming increases * TOMATOE increases * TRASH demand rises * NFT supply decreases * Market becomes active #### If burning decreases: * CINDER becomes scarce * Farming slows * TOMATOE output drops * CINDER value rises * TRASH demand stabilizes Burning is self-regulating through the three-token loop. *** ## 🌍 **9. How Burning Ties Into the Metaverse** Burning supports future expansion: * Energy grid systems * Factory NFTs * Seasonal burn events * Multi-token resource production * Partner project recycling * Global burn leaderboards * Weather-linked burn cycles * Energy routing & batteries The Incinerator becomes a long-term utility asset. *** ## πŸ§ͺ **10. Future Burning System Enhancements (Not Active Yet)** Features planned or under consideration: * πŸ”§ Incinerator Upgrade Modules * βš™οΈ Efficiency boosters * 🌦️ Weather impact on burn yield * πŸ”₯ Burn seasons with bonuses * 🏭 Multi-output burn cycles * πŸ”— Partner collection burn integration * πŸŽ– Burn ranks and achievements These will arrive gradually and balanced. *** ## πŸ›‘ **11. Safety & Final Notes** * Burns are *permanent* * No NFT can be recovered once burned * Burning is optional and player-driven * CINDER output is subject to balancing * The system evolves over time * Nothing here guarantees financial results Burning exists to power gameplay β€” not speculation. *** ## 🎯 **Summary** Burning is how players: * Destroy NFTs * Consume TRASH * Generate CINDER * Load energy * Farm TOMATOE * Loop resources * Drive the entire CleanupCentr economy The Incinerator NFT is the key piece that starts the entire chain. --- # 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: ``` GET https://the-cleanupcentr.gitbook.io/the-cleanupcentr/documentation/burning-system.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.