> For the complete documentation index, see [llms.txt](https://docs.level.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.level.finance/level-dao/lvl-weekly-burn.md).

# LVL Weekly Burn

This LVL Burn mechanism was implemented in [LIP-022: Regulating LVL Balance](https://dao.level.finance/proposals/0x1ee5e7c139d956e9f4a3a2945c6271eab9f3b700829b714eec4a8fcf1e0fe0b1) after the DAO voted in favor. This mechanism regulates the DAO’s LVL balance.

Given that the DAO accrues trading fees on a continuous basis, there will be a weekly 1:1 burning of LVL tokens from the treasury reserve for every 1$ of trading fees it accumulates.

> *We believe that reducing terminal supply of LVL at the same rate that the platform is growing is a great way to simultaneously enhance the value of the protocol as well as reward its community of early adopters committed to the long term success of the protocol.*

<figure><img src="/files/L6OtEAPNlHjOfyXjCpe7" alt=""><figcaption></figcaption></figure>


---

# 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.level.finance/level-dao/lvl-weekly-burn.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.