> For the complete documentation index, see [llms.txt](https://docs.sweep.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sweep.finance/roadmap/economic-model-expansion.md). # Economic Model Expansion Sweep’s economic model is designed to evolve continuously alongside platform activity, creating a system where value generation, distribution, and supply dynamics are directly linked to real usage. Unlike traditional models that rely on fixed reward schedules or external interventions, Sweep operates through a **self-adjusting economic structure** driven by transaction volume. As activity within the ecosystem increases, the core mechanisms of the model become stronger and more impactful. *** ### **Deflationary Mechanism** A fundamental component of the Sweep economy is its usage-driven deflationary model. * A fixed portion of all transaction activity is permanently removed from circulation * Token supply decreases as platform usage increases * Deflation is continuous and directly tied to real activity This approach eliminates the need for predefined burn events or artificial supply reductions. Instead, scarcity is created organically through sustained ecosystem usage. *** ### **Distribution Model** In parallel with deflation, Sweep integrates a volume-linked distribution system that connects user participation with measurable value return. * A portion of transaction volume is redistributed in USDT * Distribution scales proportionally with ecosystem activity * Users are incentivized through continuous participation This creates a system where engagement is directly tied to ongoing value flow, reinforcing both user retention and platform growth. *** ### **Liquidity and Market Stability** The economic model is further supported by structured approaches to liquidity and market stability. * Liquidity is strengthened through exchange expansion and strategic partnerships * Market depth increases alongside user adoption * Volatility is mitigated through continuous transaction flow This ensures that the token economy remains functional, accessible, and resilient as the ecosystem grows. *** ### **Utility Expansion** As the ecosystem evolves, the utility of the SWEEP token will expand across multiple layers. * Interaction systems drive continuous usage * Payment infrastructure introduces real-world applicability * Tokenization frameworks expand value representation This multi-layered utility structure ensures that demand is driven by actual usage rather than speculative behavior. *** ### **Self-Reinforcing Economic Cycle** The combination of these mechanisms creates a **self-reinforcing economic loop**: * Increased activity generates higher transaction volume * Higher volume strengthens deflation and distribution * Stronger incentives drive further user participation This cycle allows the ecosystem to grow organically, without relying on unsustainable reward structures. *** ### **Long-Term Sustainability** Sweep’s economic model is built for long-term sustainability. * Growth is driven by real user activity * Value generation is directly linked to participation * Supply dynamics are governed by transparent and predictable mechanisms As adoption increases, the system becomes stronger, more efficient, and more resilient. --- # 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://docs.sweep.finance/roadmap/economic-model-expansion.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.