> 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/platform-revenue.md).

# Platform revenue, buybacks and burns

The platform claims its trading fees automatically. About **60%** of that revenue is used to buy `$STONK` on the open market and burn it, and the rest is retained.

![The revenue dashboard](https://2634848750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCxPyGLkCWEEYzj4BueG%2Fuploads%2Fgit-blob-9619caa678d8f92616f1adae77a5d8759d0322d3%2Frevenue.png?alt=media)

## The cycle

Every few minutes, the platform harvests its own Fee Key on every pool, burns the launched-token fees that arrive, spends 60% of the quote-token revenue buying `$STONK` and burning it, and moves the remaining 40% to the treasury.

Fee collection runs whether or not buybacks are active. The two are separate mechanisms, and tying them together once meant that pausing buybacks quietly stopped fees being collected at all.

## What gets burned

Two different things, and they are easy to confuse.

**Fee income burns.** Launched tokens that arrive as the platform's share of trading fees are burned straight away rather than sold.

**Buyback burns.** `$STONK` bought on the open market with revenue is burned immediately after the purchase.

Both permanently reduce supply, and both are visible on the revenue page.

## Fees paid in `$STONK`

![Fees paid in STONK](https://2634848750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCxPyGLkCWEEYzj4BueG%2Fuploads%2Fgit-blob-931d8049a181e65c94d91bb51c60f5bde01cd68c%2Frevenue-stonk-fees.png?alt=media)

Launches priced *in* `$STONK` pay their trading fees in `$STONK`. There is nothing to buy back, so the 60% share is burned on the spot and the rest goes to the treasury.

`$STONK`'s own pool earns fees in `$STONK` too. That half is not split at all, and goes to the treasury in full.

## What the revenue page reports

![Traded volume](https://2634848750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCxPyGLkCWEEYzj4BueG%2Fuploads%2Fgit-blob-67285cbb4b2f72320c8b69994ecc5c598528ae4f%2Frevenue-volume.png?alt=media)

| Figure                 | Meaning                         |
| ---------------------- | ------------------------------- |
| RWA volume             | Volume on tokenized-asset pairs |
| Total volume (Raydium) | Every pool StonkFun created     |
| Total volume           | All venues                      |

These are measured on-chain: every swap is decoded from its pool's own events and reconciled against that pool's vaults, then priced from the quote assets' own markets. RWA volume is a subset of Raydium volume, which is a subset of the total.

![Revenue stat cards](https://2634848750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCxPyGLkCWEEYzj4BueG%2Fuploads%2Fgit-blob-9cc6ea08c2d4b536347cb12e563b0f66f5760f30%2Frevenue-stats.png?alt=media)

| Figure          | Meaning                                                                   |
| --------------- | ------------------------------------------------------------------------- |
| Total revenue   | Trading fees paid to the platform, valued at the time they were claimed   |
| Total buybacks  | USD spent buying `$STONK` on the open market                              |
| `$STONK` burned | Current value of all the STONK destroyed, from buybacks and fees together |

![Buyback and burn charts](https://2634848750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCxPyGLkCWEEYzj4BueG%2Fuploads%2Fgit-blob-1fa710ce34b177bff58c0d57639822b1afc17322%2Frevenue-charts.png?alt=media)

## Reading it over the API

```bash
curl 'https://www.stonkfun.xyz/api/public/v1/revenue'
curl 'https://www.stonkfun.xyz/api/public/v1/revenue/history'
```

The history endpoint returns the whole daily series in one response, keyed by UTC day, in USD. There is no date parameter by design: fetch it once and index it locally.

| Field                  | Meaning                                                        |
| ---------------------- | -------------------------------------------------------------- |
| `dailyRevenue`         | Quote-token fees claimed to the treasury, valued at claim time |
| `dailyHoldersRevenue`  | The share spent buying the platform token back and burning it  |
| `dailyProtocolRevenue` | The remainder                                                  |
| `coverage`             | Rows carrying no USD price, which therefore count as zero      |

Fees earned by creator positions and by reward-holder positions are claimed directly from Raydium and are not included in these figures.

## A note on precision

A buyback burns exactly what its swap received, measured from the resulting balance rather than from the quote it was given. With variable slippage the fill differs from the quote, and burning the quoted amount would be wrong in both directions.


---

# 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/platform-revenue.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.