> For the complete documentation index, see [llms.txt](https://docs.chainspin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chainspin.com/economics/supply-and-circulation.md).

# Supply & Circulation

The total supply of $SPIN is fixed at 1,000,000,000. The contract has no mint function after the token generation event, so no new tokens are ever created. What changes over time is not the total supply but how much of it is in circulation.

Tokens reach the community from the Player Rewards & Airdrops allocation, 125,000,000 $SPIN or 12.5% of supply, which is set aside at launch and released on a published schedule. Release categories include:

* Player rewards
* Seasonal competitions
* Staking incentives
* Ecosystem growth grants

The release schedule is designed to decline over time, so the rate at which tokens enter circulation slows as the platform matures and the weekly buyback takes over as the engine.

Working in the other direction, the buyback permanently removes tokens from circulation every week. See [Buyback & Burn](/spin-token/buyback-and-burn.md) for how that works, and [Vesting](/spin-token/vesting.md) for the full unlock timeline.


---

# 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.chainspin.com/economics/supply-and-circulation.md?ask=<question>&goal=<endgoal>
```

`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.