> 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/long-term-deflation-dynamics.md).

# Long-Term Deflation Dynamics

A key characteristic of the Chainspin token economy is the interplay between **scheduled releases and burns**. Tokens reach circulation from pre-allocated pools on a published, declining schedule, while the weekly buyback permanently removes tokens from circulation. Over time, this dynamic produces a transition from an expanding circulating supply to a contracting one.

**The simplified model can be expressed as:**

<mark style="color:yellow;">Net Circulating Supply Change = Scheduled Releases − Burn</mark>

<mark style="color:yellow;">When burn exceeds scheduled releases:</mark>

<mark style="color:yellow;">Net Circulating Supply Change < 0</mark>

At this point, the circulating supply begins to contract.

Because the total supply is fixed at 1,000,000,000 and cannot be added to, every token burned reduces the maximum supply permanently. This structural scarcity can significantly increase token demand if platform activity continues to grow.


---

# 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/long-term-deflation-dynamics.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.