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

# Burning mechanism

FNT is meticulously crafted for mutual benefit, where every facet of the project is intentionally designed to realize the concept of synergistic gain. The company strategically repurchases and burns up to 50% of its revenue, employing this burning mechanism to diminish the total number of tokens in circulation steadily. Within the FNT Ecosystem, FNTIO tokens are essential for every utility, ensuring that all system activities generate revenue for FNT. As part of its sustainable ecosystem, FNT consistently repurchases tokens from the public market, initiating a controlled burn of a specific token quantity. This continuous process actively reduces the circulating token supply, creating a system that operates seamlessly like a well-oiled machine. With each action taken by FNT or involving FNT, the value experiences continuous growth, ultimately rewarding the entire community.


---

# 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://fnt.gitbook.io/fnt-whitepaper/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.
