> For the complete documentation index, see [llms.txt](https://docs.alphadune.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alphadune.com/dune-token/buy-and-burn-program.md).

# Buy & Burn Program

The Buy & Burn Program directly connects the success of Alpha Dune applications to the value of the DUNE token. By using a portion of app profits to repurchase tokens from the open market and permanently remove them from circulation, this program ensures holders benefit every time the ecosystem grows.

**Key Mechanics**:

* A percentage of profits from **Loot Dynasty, Tile Rituals, and future apps** is allocated for buybacks.
* Tokens are purchased through **open market liquidity pairs**, injecting fresh liquidity into the ecosystem.
* All purchased tokens are **burned permanently**, reducing total circulating supply.
* This mechanism creates a **direct link between app adoption and token value appreciation**.


---

# 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.alphadune.com/dune-token/buy-and-burn-program.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.