> 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/token-demand-pressure-model.md).

# Token Demand Pressure Model

The Chainspin token economy is designed so that platform usage directly translates into token demand. This mechanism is achieved through a revenue-linked buyback system that channels a portion of platform profits into the open market to purchase $SPIN tokens.

The result is a feedback loop in which increased wagering activity leads to increased token demand, creating alignment between player engagement and token value.

#### **Core Economic Flow**

<figure><img src="/files/BsAqTlrn2EKsTRp912PW" alt=""><figcaption></figcaption></figure>

#### Fundamental Buyback Formula

<mark style="color:yellow;">Token Buyback Demand = (Wager Volume × House Edge × Buyback Allocation) ÷ Token Price</mark>

#### Step-by-Step Revenue Derivation

<details>

<summary><strong>Wager Volume</strong></summary>

<mark style="color:yellow;">W = Total wagering volume</mark>\ <mark style="color:yellow;">Example: W = $1,000,000,000 monthly wagering volume</mark>

</details>

<details>

<summary><strong>Platform Revenue</strong></summary>

Revenue is derived from the platform house edge. Let E = Average house edge. Typical online gambling edge ranges between **2% – 5%** depending on game type.

<mark style="color:yellow;">Revenue = W × E</mark>\ <mark style="color:yellow;">Revenue = $1,000,000,000 × 3% =</mark> <mark style="color:yellow;">**$30,000,000 monthly**</mark>

</details>

<details>

<summary><strong>Buyback Allocation</strong></summary>

A portion of platform revenue is used to buy back $SPIN. Let B = Buyback allocation percentage.

<mark style="color:yellow;">B = 15%</mark>\ <mark style="color:yellow;">Buyback Capital = $30,000,000 × 0.15 =</mark> <mark style="color:yellow;">**$4,500,000**</mark>

<br>

</details>

<details>

<summary><strong>Token Demand</strong></summary>

The buyback capital is used to purchase $SPIN tokens on the open market. Let P = Token price.

\ <mark style="color:yellow;">Tokens Purchased = Buyback Capital ÷ P</mark>\ <mark style="color:yellow;">= $4,500,000 ÷ $0.12 =</mark> <mark style="color:yellow;">**37,500,000 SPIN**</mark>

</details>

#### Monthly Demand Example

| METRIC                                              | VALUE                                                                 |
| --------------------------------------------------- | --------------------------------------------------------------------- |
| Monthly Wager Volume                                | $1B                                                                   |
| House Edge                                          | 3%                                                                    |
| Buyback Allocation                                  | 15%                                                                   |
| Token Price                                         | $0.12                                                                 |
| Platform Revenue                                    | $30M                                                                  |
| Buyback Capital                                     | $4.5M                                                                 |
| <mark style="color:yellow;">Tokens Purchased</mark> | <mark style="color:yellow;">37.5M SPIN (3.75% of total supply)</mark> |

#### Demand Elasticity

An important feature of the model is **automatic scaling**. If wagering volume increases, buyback demand increases proportionally.

<mark style="color:yellow;">Token Demand ∝ Wager Volume</mark>\
\ <mark style="color:yellow;">// If wagering doubles:</mark>\ <mark style="color:yellow;">W₂ = 2W₁ → Token Demand₂ = 2 × Token Demand₁</mark><br>

#### Deflationary Feedback Loop

<figure><img src="/files/QuhL1IHXfG41gQRrYUso" alt=""><figcaption></figcaption></figure>

This mechanism allows $SPIN to function as a **growth-linked economic asset rather than a passive reward token**.

#### Long-Term Supply Dynamics

Over time, the interaction between **buybacks, staking lockups, and ecosystem demand** can significantly reduce liquid token supply. Three forces contribute to supply compression:

* Buyback and burn programs
* Staking lockups for platform benefits
* Treasury reserves and ecosystem allocations

Together, these mechanisms reduce circulating liquidity while platform usage continues to generate demand.

#### Strategic Implications

The Token Demand Pressure Model positions $SPIN as a **platform-embedded utility asset** rather than a purely speculative token. Key characteristics include: demand tied directly to wagering activity, revenue-driven buybacks, deflationary supply pressure, and incentive alignment between users and token holders.

As Chainspin scales, the economic throughput of the platform becomes the primary driver of token demand.


---

# 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/token-demand-pressure-model.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.