# Token economics {% hint style="warning" %} **The Oxen Network has transitioned to the Session Network. More information** [**here**](https://oxen.io/blog/development-is-transitioning-to-session-token)**.** {% endhint %} The Oxen network is run by a decentralised network of incentivised nodes called [service nodes](https://docs.oxen.io/oxen-docs/about-the-oxen-blockchain/oxen-service-nodes). As the workhorses of the network, service nodes get the lion's share of the reward: **16.5 $OXEN per block**. This results in the creation of **11,880 $OXEN per day**. Because of the nature of [Pulse](https://docs.oxen.io/oxen-docs/about-the-oxen-blockchain/pulse-pos-on-oxen), a large proportion of $OXEN's total supply is locked in service nodes and unavailable on the market. On top of this, our research has shown that people earning rewards through staked nodes are **much** more likely to hold their tokens and continue participating in the network than those who earnt their tokens via mining. These two qualities help increase buy pressure and decrease sell pressure in $OXEN markets, respectively. More details about the cryptoeconomic theory which underpins Oxen [can be found here](https://loki.network/wp-content/uploads/2019/05/Loki_Cryptoeconomics-2-1.pdf). The not-for-profit[ Oxen Privacy Tech Foundation](https://optf.ngo/) receives a governance reward of 9240 $OXEN every 7 days. This reward is used to pay for development, marketing, and community projects, more information about how the Oxen treasury and governance reward is managed can be found on the [OPTF](https://optf.ngo/) website. --- # Agent Instructions: 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: ``` GET https://docs.oxen.io/oxen-docs/about-the-oxen-blockchain/oxen-token-economics.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.