> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/higher-learning/bsv-academy/deep-dive-in-bsv-blockchain/supply-policies-and-reward-mechanisms/token-supply-policy.md).

# Token Supply Policy

<figure><img src="https://3421145409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRTEKu4E7Fvtss3GI9CYU%2Fuploads%2Fd3jAeQsMEfKVemQ1SLpc%2FSlide16.jpg?alt=media&amp;token=bc52599a-0860-4044-8db6-5192040e10ff" alt=""><figcaption></figcaption></figure>

The total supply of BSV is capped at **21 million coins**, with each coin being divisible into **100,000,000 satoshis**. This results in:

* **Total Supply**: **2.1 quadrillion satoshis**, which is ample for global-scale applications.
* **Fixed Supply**: The supply is hardcoded into the protocol, ensuring that it cannot be altered or **inflated**.
* **Deflationary Effect**: The fixed nature of the supply encourages **utility usage** over speculative trading.

Distribution of BSV occurs through **mining rewards**, which are allocated to nodes that successfully create new blocks. This mechanism promotes a **stable economic environment** conducive to long-term growth.


---

# 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://hub.bsvblockchain.org/higher-learning/bsv-academy/deep-dive-in-bsv-blockchain/supply-policies-and-reward-mechanisms/token-supply-policy.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.
