# Deflationary Token

Imagine a Web3 Games where players can create unique items using $DOHKO. To create an epic item, the player would need to burn a significant amount of tokens. Not only would this make the item more unique, but it would also reduce the total supply of $DOHKO.

DOHKO's deflation strategy is set against a backdrop of careful economic planning, ensuring that, as the project evolves, tokenomics remains robust and beneficial for all participants in the ecosystem. 

Some of the strategies to be implemented:

### <mark style="color:orange;">**Increased Burn Rates for Stakers**</mark>

Stakers who keep their tokens for an extended period could have lower burn rates or even exemption.

### <mark style="color:orange;">Use of Tokens in Game Mechanics</mark>

**Creation of Rare Items:** The creation of rare items in games that require the burning of tokens to acquire. **Character Upgrades:** The possibility of using tokens to perform character upgrades, with a percentage of the tokens being burned in the process.

### <mark style="color:orange;">**Burning Votes**</mark>

The community will be able to vote on proposals to burn tokens at specific times, increasing the sense of belonging and participation.&#x20;

### <mark style="color:orange;">**Strategic Partnerships**</mark>

**Integration with Other Projects:** Partnerships with other projects to create synergies and increase demand for $DOHKO, leading to greater token burning.


---

# 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://dohko.gitbook.io/whitepaper/dohko-token/deflationary-token.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.