> For the complete documentation index, see [llms.txt](https://docs.unich.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unich.com/unich-network/freenomics/supply-design-philosophy.md).

# Supply Design Philosophy

FC supply must directly reflect the level of participation and value the network generates. Unlike Bitcoin - a fixed supply of 21 million, issued on a predetermined halving schedule independent of adoption. Unich Network combines **flexible supply tied to the network** with the [**Node-count-based halving mechanism**](/unich-network/mining-and-node-upgrade-mechanism/base-mining-rate-and-the-halving-mechanism.md)

The logic: when a Peer Meet is verified, value is created for two Users (a real relationship) and for the network (a trusted connection added). Upgrading both Nodes' Mining Rates directly reflects real development. The more real connections the network has, the more FC is produced; the more stagnant the network, the slower FC is produced. The halving mechanism ensures total supply is not infinite — when the network reaches 800 million Nodes, the base Mining Rate reaches 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 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.unich.com/unich-network/freenomics/supply-design-philosophy.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.