> For the complete documentation index, see [llms.txt](https://docs.maicrotrader.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maicrotrader.com/8.-usdmaicro-token-full-tokenomics/8.4-flywheel-mechanics.md).
# 8.4 Flywheel Mechanics
### Flywheel Mechanics
The token economy compounds through five interlocking loops. Each loop reinforces the others.
**Loop 1: Fee Flow** Vault deposits generate trading volume. Volume generates fees. Fees fund buybacks. Buybacks reduce circulating supply and reward stakers.
**Loop 2: Burn Loop** As platform usage grows, 75% of each buyback is permanently removed from supply. Deflationary pressure increases as TVL and STA count scale. The token becomes structurally scarcer as the platform becomes more successful.
**Loop 3: Staker Yield** Staking locks tokens from circulation, reducing float. Stakers earn fee-derived yield without new issuance. Higher yield attracts more stakers, which reduces float further, which increases price support per unit of buyback spend.
**Loop 4: Creator Loop** Creators bond $MAICRO to publish strategies. Successful strategies attract depositor capital. More capital generates more fees. Fees pay creator royalties and fund buybacks. Successful creators build reputation, attract more depositors, deepening the loop.
**Loop 5: Demand Loop** Capability tiers require staking. As the Strategy Builder adds more configuration depth and ATA access, the value of being at higher tiers grows. Demand for staking positions grows with platform capability, independent of speculative price action.
#### Formal Flywheel Equation
The flywheel's self-reinforcing property can be expressed as:
```
TVL(t+1) = TVL(t) × (1 + g_strategy + g_depositor)
where:
g_strategy = new STA deployments × average capital per STA
g_depositor = ATA inflow driven by published track records
Fee_Revenue(t) = TVL(t) × Fee_Rate
Buyback_Volume(t) = Fee_Revenue(t) × Buyback_Rate
Burn_Rate(t) = Buyback_Volume(t) × 0.75
Circulating_Supply(t+1) = Circulating_Supply(t) - Burn_Rate(t)
Staker_Yield(t) = (Buyback_Volume(t) × 0.25) / Total_Staked(t)
```
The key property: as long as TVL grows, fee revenue grows, buyback volume grows, burn accelerates, and staker yield improves, all simultaneously. The loops do not compete. They compound.
***
### Supply Trajectory
At current burn mechanics and projected usage growth, the circulating supply declines monotonically as long as the platform is generating fees. The loyalty unlock model (20% of mining rewards requiring sustained vault deposits) also reduces sell pressure at each vesting cliff by ensuring the final and largest tranche only reaches depositors who are still engaged with the platform.
Team tokens vest linearly from July 2025 to July 2028, with a 6-month cliff. No team tokens enter circulation before July 2025. The vesting schedule is on-chain and verifiable.
***
*Exact staking tier thresholds and bond rates are pending final confirmation and will be published prior to Strategy Builder launch.*
---
# 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.maicrotrader.com/8.-usdmaicro-token-full-tokenomics/8.4-flywheel-mechanics.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.