> For the complete documentation index, see [llms.txt](https://docs.sia.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sia.tech/miscellaneous/siacoin-total-supply.md).

# Siacoin Total Supply

The total supply of Siacoins (SC) is unlimited; there will never be a cap on the number of Siacoins generated. The amount of data that can be stored grows over time, and as Sia is used to store more data, the network requires more Siacoins to fund the associated contracts.

As of June 6, 2025, approximately 60.5 billion coins have been created, with the new coin introduction slowing down as each new block is produced.

Additionally, miners would lose their incentive to continue providing services to the network if the block reward were to cease.

## Creation of new Siacoins

New Siacoins are created through proof-of-work mining. Over 56 billion Siacoins are circulating, and that number will continue to increase. Storing more data on the network requires more Siacoins to fund storage contracts.

{% hint style="info" %}
The number of Siacoins created for each block is 300,000 minus the height. This means a block with a block height of 200,000 has created 100,000 Siacoins. After a height of 270,000, the block reward won't get lower, and all blocks will have a reward of 30,000 Siacoins.
{% endhint %}

## Supply structure changes

Sia version 1.5.4 introduced a network hard fork that established the Sia Foundation, a non-profit organization that supports, develops, and promotes the Sia network. This changed the supply structure: the Foundation receives funding through a block subsidy of 30,000 Siacoins per block, disbursed every 4,380 blocks. The hard fork also included an initial offering of approximately 1.57 billion Siacoins to fund the Foundation's initial operations.

This caused a temporary increase in the inflation schedule for a single year, of a few percentage points, before returning to near pre-fork levels.

## Siacoin inflation

Inflation accommodates factors that reduce the number of coins in circulation. These include coins locked in contracts as collateral, lost coins, and coins burnt due to failed storage contracts. Over time, inflation diminishes, but it continues to secure the network by providing block rewards to miners.

| Year                | % Growth in total Siacoins |
| ------------------- | -------------------------- |
| 1                   | 90                         |
| 2                   | 39                         |
| 3                   | 21                         |
| 4                   | 11.6                       |
| 5                   | 4.6                        |
| 6 (Foundation year) | 9.9                        |
| 7                   | 6.3                        |
| 8                   | 5.9                        |
| 9                   | 5.6                        |
| 10                  | 5.3                        |
| 20                  | 2.3                        |


---

# 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://docs.sia.tech/miscellaneous/siacoin-total-supply.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.
