# Forecasted Release and Burning

In the Stavax ecosystem, gas fees are settled and consumed within StaMech through a burning mechanism.

The daily issuance of $ndSTA by STA-Nodes is intricately tied to the combined current total supply of $STA and $ndSTA. As Stavax is incinerated as gas within the ecosystem, its total supply decreases.

Similarly, the total supply of $ndSTA diminishes as $ndSTA is burned during the redemption process based on user inputs.

Once the total supply reaches approximately half of the maximum total supply, daily emissions begin to decrease. The reduction continues each time the total supply increases by half of the previous threshold value. &#x20;

Simultaneously, the dynamic halving introduces constraints on the overall supply by exerting negative pressure on circulating token quantities.

The Maximum Total Supply of $STA $ndSTA amounts to 600,000,000 tokens. The fundamental Release Tranches are outlined as follows:

<figure><img src="/files/VVdgTdMoGRhHyhHGlRXz" alt="" width="375"><figcaption></figcaption></figure>

…etc. This pattern continues forever.&#x20;

85% of $ndSTA emissions are dedicated to supporting the crucial operations of STA-Nodes, contributing to the network's integrity and stability. The remaining 15% is designated for a gas subsidy node, aimed at facilitating a gasless experience for players. This allocation reduces friction on the chain and is expected to boost transaction volume by enhancing user experience.

\ <br>


---

# 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://whitepaper.starmech.io/v.-tokenomics/forecasted-release-and-burning.md?ask=<question>
```

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.
