> For the complete documentation index, see [llms.txt](https://starck.gitbook.io/starck-whitepaper-v.3.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://starck.gitbook.io/starck-whitepaper-v.3.0/stk-token-burn-program.md).

# STK Token Burn Program

Starck's Token Burn program is one of the main strategies of the project to drive up the value and reduce the total supply of **STK** tokens.

Through carefully planned burns directly through the token's smart contract, **Starck** aims to increase the rarity and market value of its tokens while engaging and rewarding the community of STK token holders.

**Main features of Starck Burn Program:**

**Drastic Reduction in Supply**

**Reduction Target**: The program aims to reduce the total supply of STK tokens by 90% over a period of five years. This means burning 900 million tokens from the initial supply of 1 billion, leaving only 100 million tokens in circulation.

**Planning:** Burns are structured in the **Starck** Burning Roadmap, which details the stages and timelines for token burns. This involves regular burns at set intervals that are performed transparently and predictably.

**Starck Burning Roadmap**

**Burn Phases**: The roadmap sets out the key moments for token burn, with each phase clearly defined. This provides the community with full transparency on upcoming burns and their effects on supply.

**Transparency and Traceability**: All burns are publicly documented and traceable on the blockchain, ensuring that the process is fully transparent and verifiable by anyone

**Community Engagement**

**Active Participation**: The burn program encourages the active participation of token holders. The community plays an important role in the process by being able to participate in special events and initiatives related to the token burn.

**Value of Burning Program for Investors**

**Increasing Rarity and Value:**

Reducing the total supply by burning tokens creates the conditions to increase the rarity and value of the remaining tokens. This makes **STK** tokens more attractive to long-term investors and boosts their market demand.

**Long Term Return Strategy:**

The burn program is a key element of **Starck**'s long-term strategy to ensure a sustainable increase in token value. By gradually reducing supply, the project creates favorable conditions for long-term returns and stability.

**Token Value Support:**

Through regular burns, **Starck** maintains the value of STK tokens and builds trust among investors that the project is committed to maintaining and growing their investment.

**Conclusion**

The **Starck** Token Burn Program is a strategic initiative that aims to increase the value of **STK** tokens. With its transparent implementation and commitment to the community, the program plays a key role in Starck's long-term strategy for value creation and sustainable growth.

Check out the Burning Roadmap section where all burning criteria are described.


---

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