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

# 🔥 Token Burning Mechanism

The **Faith Protocol** employs a strategic **token burning mechanism** designed to manage its token supply effectively and support its long-term value. This system reduces the total token supply, creates scarcity, and boosts token demand. Here are the main types of token burns:

***

**1. Scheduled Burns 📅**

These are pre-planned burns that happen at regular intervals, as defined in the protocol’s roadmap. Scheduled burns are an essential component of **FAITH** token management, providing a reliable and consistent reduction in supply over time.

* **Use Case**:
  * By periodically reducing the supply of **FAITH** tokens, scheduled burns contribute to **scarcity**, which in turn can help increase demand and stabilize the token’s value.
  * The predictable nature of scheduled burns makes them transparent and reliable for investors and the community.
* **Example**: A burn event every quarter where 1% of the total circulating supply of **FAITH** tokens is destroyed, reducing the total available supply over time.

***

**2. Event-Based Burns 🎉**

Event-based burns take place during significant **Faith Protocol** events, such as platform updates, major milestones, new product launches, or promotional campaigns. These burns are linked directly to important moments within the ecosystem, making them an exciting and timely way to reduce supply.

* **Use Case**:
  * These burns aim to align the token’s value management with **high-profile events**, creating an association between protocol achievements and token value growth.
  * Event-based burns can generate excitement and additional interest within the community, as people look forward to special promotions or updates.
* **Example**: When the **Faith Meta Human** reaches 1 million active users, a burn of 2% of the circulating **FAITH** supply occurs, rewarding community growth and enhancing scarcity.

***

**3. Community Burns 🌍**

Community-driven burns are based on active participation from the **Faith Protocol** community. These burns are often initiated through **community voting** or user metrics, where the protocol listens to its users and burns tokens to reward them or acknowledge their contributions.

* **Use Case**:
  * This type of burn makes the **FAITH** token more **democratic** and gives community members a sense of involvement in token management. It fosters greater engagement and allows users to feel like active participants in the ecosystem.
  * Community-driven burns can reward users for achievements like staking, farming, or engagement with **Faith Farming** or **Meta Education** services.
* **Example**: After a community poll, users vote to burn 500,000 **FAITH** tokens to celebrate the launch of a new virtual property feature or the completion of a major milestone in **Faith City**.

***

#### **The Power of Token Burning 🔑**

The **Faith Protocol’s token burning mechanism** consists of three major strategies—**Scheduled Burns**, **Event-Based Burns**, and **Community Burns**—all designed to reduce the supply of **FAITH** tokens and ensure their value remains robust.

* **Scheduled Burns** provide **predictability** and a steady reduction in supply, reinforcing long-term value stability.
* **Event-Based Burns** tie token burning to important protocol milestones, increasing engagement while aligning value with progress.
* **Community Burns** empower the ecosystem’s users to play an active role in shaping the protocol's future, making the process more inclusive and democratic.

Together, these approaches provide a **comprehensive, user-centered** way to enhance the value of **FAITH** over time, supporting the growth of the entire **Faith Protocol** ecosystem.


---

# 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://faith-protocol.gitbook.io/faith-protocol-whitepaper/token-burning-mechanism.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.