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

# DeSo Tokenomics

DESO is the native token of the DeSo Blockchain. It is burned as a fee on every single transaction that is processed by the network, making it inherently scarce over time. It is also used to stake to nodes to secure the network as part of [DeSo's Revolution Proof of Stake Consensus](https://revolution.deso.com). The staking APY is subject to change, update-able by PoS hard fork (see [DeSo Governance](/deso-governance.md)), and [is always listed on the block explorer's validator page](https://explorer.deso.com/validators).

Simply put, the more transactions that run through the DeSo network, the more fees are burned, and the more scarce the currency. In the short-term, the APY paid to support staking is inflationary, but staking rewards will be lowered over time, and in the short-term they encourage users to stake their DESO, which also has a deflationary effect.

In addition, apps launched by the Core Team, such as [Focus](https://focus.xyz) ([docs](https://docs.google.com/document/u/1/d/14Um8ErmoE8IhgZrACSI2FeTo2yji2Q1Hxvw7KNoozM8/edit)) and [Openfund](https://openfund.com) ([docs](/openfund/what-is-openfund.md)) serve as [DESO Sinks](/deso-tokenomics/deso-sinks.md).

**Read the next section to learn about DeSo's founding story, initial supply distribution, and more.**


---

# 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.deso.org/deso-tokenomics.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.
