> 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.md). # Economics - [Supply & Circulation](https://docs.chainspin.com/economics/supply-and-circulation.md): How $SPIN reaches circulation from a fixed supply: scheduled releases from the Player Rewards pool, offset by the weekly buyback. - [Long-Term Deflation Dynamics](https://docs.chainspin.com/economics/long-term-deflation-dynamics.md): How scheduled token releases and weekly burns interact over time to move $SPIN from an expanding circulating supply to a contracting one. - [Token Demand Pressure Model](https://docs.chainspin.com/economics/token-demand-pressure-model.md): The model linking Chainspin wagering volume to $SPIN demand, showing how house edge and buyback allocation translate into tokens bought off the market. - [Liquidity & Market Infrastructure](https://docs.chainspin.com/economics/liquidity-and-market-infrastructure.md): The exchange, liquidity pool and market maker infrastructure planned to support $SPIN trading and price discovery. --- # 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.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.