> For the complete documentation index, see [llms.txt](https://docs.metaverse-ico.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metaverse-ico.net/whitepaper/native-token/token-burning/constant-burning.md).

# Constant Burning

While investors and Metachain users are financially protected – thanks to the unstoppable supply restriction by MetaChain and the indefinitely **constant burning mechanism** that continues in high amounts at the beginning and then decreases –, META gains value day by day because of the supply-demand balance. For all MetaCoins that are not sold during the presale phase, a burn pool is created, and unsold MetaCoins are transferred to this pool. These are burned through the Auto-Burn mechanism.

Auto-Burn is a formula that guarantees that the maximum META is removed from the circulation in the optimum time without leaving the burning process to the initiative of the individual.

```
M = ((MB × 13.104) / (100 × LP + S)) × (Cos(n × 10⁻⁹ + 86) × 2.923)
```

| Symbol | Description                           |
| ------ | ------------------------------------- |
| **M**  | Amount of MetaCoins to Burn           |
| **LP** | Liquidity Price                       |
| **MB** | Number of Blocks Produced in 2 Months |
| **S**  | Variable Value (Initial Value: 1000)  |
| **n**  | Total Burned MetaCoins                |

**With the Auto-Burn formula, burning is performed regularly in 2-month periods, inversely proportional to the** META **price.**

Under the Cos90=0 valuation, the formula remains unchanged until unsold METAs are burned.


---

# 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://docs.metaverse-ico.net/whitepaper/native-token/token-burning/constant-burning.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.