> For the complete documentation index, see [llms.txt](https://stonkfun.gitbook.io/stonkfun-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stonkfun.gitbook.io/stonkfun-docs/earning/ecosystem-flywheel.md).

# The Ecosystem Flywheel

A share of every reward pool's trading fees flows to the flywheel, which buys back and burns the platform's top 15 tokens by market cap, weighted by market cap, every few minutes.

![The flywheel board](https://2634848750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCxPyGLkCWEEYzj4BueG%2Fuploads%2Fgit-blob-f3271d3fb95776e7c6269feef5f07a3d4f49efe7%2Fflywheel-board.png?alt=media)

## How it is funded

Every reward launch locks two positions: 90% of the liquidity to the platform, and 10% to the flywheel.

That 10% earns 0.1% of the pool's volume, continuously, for as long as the pool trades. Since it is a locked position, that revenue stream cannot be withdrawn or turned off.

## What it does with the money

Revenue is pooled across every reward launch. The platform's tokens are ranked by market cap, the top 15 are taken, and the pot is split across them by weight. Each share is used to buy that token on the open market, and everything bought is burned.

Tokens that drop out of the rankings keep their history and resume the moment they climb back in.

## `$STONK` is never a target

The platform token is excluded from the rankings entirely.

It has its own dedicated buyback engine already, and it dwarfs every launched token by market cap. At one point it would have taken 64.6% of the roster's weight on its own, which would have turned the ecosystem flywheel into a second `$STONK` buyback.

## When a tick spends

A round only executes once the pot is large enough to reach the whole roster rather than just the top-weighted token. Below that, the money accumulates and the round is skipped.

Without that rule, a small pot funds one buyback and the board reads "it only ever buys the top token". Rounds fire less often but spread fully, and the same money is spent either way.

A target too small to be worth a transaction in a given round is skipped, and its weight rolls into the rest.

## The board

[`/flywheel`](https://www.stonkfun.xyz/flywheel) is read-only and updates on the flywheel's own cadence.

| Stat                 | Meaning                                          |
| -------------------- | ------------------------------------------------ |
| Bought back & burned | Lifetime USD, valued at the time of each buyback |
| Buybacks executed    | Each one a swap and a permanent burn             |
| Tokens reached       | Distinct tokens ever bought back                 |

The **Current rankings** panel shows what the next round will split across, by weight. The **Recent buyback burns** panel links every burn transaction on Solscan.

A row showing a dash and "ranking…" is a token whose market cap has not loaded yet, not one the flywheel has stopped buying.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://stonkfun.gitbook.io/stonkfun-docs/earning/ecosystem-flywheel.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.