> For the complete documentation index, see [llms.txt](https://docs.injex.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.injex.fi/injex-in-details/injex-finance-tokenomics/token-burning-strategy.md).

# Token Burning Strategy

The proposed token burning plan is designed to incentivize trading activity, reduce circulating supply, and contribute to the long-term value of the $INJX token.

### Burning Mechanism

**Revenue Share Burns**: Injex Finance implements a progressive burning mechanism based on token revenue sources to ensure sustainable growth and value appreciation.

**Periodic Burns**: Scheduled quarterly or bi-annual community-determined burns. This approach provides predictability and control, fostering community engagement.

### Burning Ratios

The burning ratio will expand over time, including token sources such as a percentage of the revenue generated from sponsored listings, token utility, partner fees, and data services.

<br>


---

# 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:

```
GET https://docs.injex.fi/injex-in-details/injex-finance-tokenomics/token-burning-strategy.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.
