# Token Burn Program in Tokenomics

A strategic place in **Starck** Tokenomics**/ STK/** is the token burning program. The purpose of the mass burn of 90% of the total supply is to regulate the number of tokens in circulation and increase the value of the project in the long term.

**Burn Process**

Burning is done via the **STK** smart contract, with burned tokens permanently removed from circulation.

**Burns Every Quarter**

Tokens are burned every quarter as the sum of all completed points in **Starck's** Burn Roadmap.

**Burn Categories**

Stake and reinvestments

Airdrop campaigns

Liquidity in exchanges

Community vote

User burns in *asip.starck.app*

**Impact on Tokenomics of the project**

After the implementation of the BURN Roadmap, the number of tokens will be reduced from **1 billion** to **100 million** for a maximum period of five years or after the implementation of the points set in the roadmap.

The remaining number of tokens after the drastic reduction will be distributed in different categories for the development of the project.

**Increase in Value**

The reduction in quantity is intended to increase the value of the remaining tokens, encouraging long-term holding and investment.

**Community Engagement**

Token burning is a means of encouraging community activity and engagement, with token holders being able to participate in the process and contribute to the development of the project.

**Conclusion:**

The token burning program is an essential component of Starck Tokenomics. It provides sustainable management of the number of tokens, increases their value and engages the community in the long-term success of the project.


---

# 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://starck.gitbook.io/starck-whitepaper-v.3.0/token-burn-program-in-tokenomics.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.