# 🔥 Buy and Burn

*The Blaze token is throwing the hottest party in town, with a blazing strategy to increase its value. It's a slow burn, with daily token barbecues torching it. So, grab your marshmallows and watch the limited supply go up in smoke!* 

### **Decentralized Buy and Burn Strategy**

**ETH Allocation for Buy and Burn:** In this DeFi protocol, 20% of ETH earnings from auctions fund a Buy and Burn mechanism.

**Execution Process:** Tokens are bought from the TITANX/ETH pool, then TitanX tokens are used to acquire BLAZE from Blaze/TitanX pool.

### **Token Burning Approach**

**Strategic Approach:** The strategy aims to reduce the circulating supply of Blaze tokens to enhance scarcity.

**Daily and Special Burns:** Daily burns involve up to $100,000 ETH for TitanX purchase and Buy and Burn for Blaze, ensuring decentralized execution.

### Special Burn Events

A "Bonfire Party" event begins on TitanX day 288 and every 108 Days after that, where 10% of the ETH set aside for the for Buy and Burn is allocated.

### **Strategic TitanX Purchase**

On TitanX day 280, 11 trillion TitanX will be released, when Blaze bonfire party is lit.

### **Maintaining Decentralization**

The protocol ensures transparency and consistency, with no changes made by developers, emphasizing true DeFi principles. The goalposts don't change.

<figure><img src="/files/d5QTHNuUpuqQUSoWEGVv" alt="" width="563"><figcaption></figcaption></figure>


---

# 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.titanblaze.win/burn-paper/buy-and-burn.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.