> 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/bsv-basics-protocol-and-design/introduction-to-bitcoin-protocol-and-design/digital-scarcity.md).
# Digital Scarcity
Another pivotal concept introduced by Bitcoin is **digital scarcity**. Within the Bitcoin protocol, there exists a finite supply of bitcoins, capped at **21 million** created and set aside at the launch of the network. The smallest unit of a bitcoin, known as a **"satoshi,"** represents **1/100,000,000th** of a bitcoin.
This limitation on supply ensures that no more than 21 million bitcoins will ever be emitted through the **block reward subsidy**, establishing Bitcoin as a **digitally scarce asset**.
This scarcity mustn't be seen as a gimmick to pump the coin's price. Rather, the limitation on coin supply **incentivises miners to remain in the network** they've invested in thus far, to process millions and billions of **meaningful transactions** and **charge fees** as the block reward subsidy diminishes towards zero.
---
# 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/bsv-basics-protocol-and-design/introduction-to-bitcoin-protocol-and-design/digital-scarcity.md?ask=&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.
