> For the complete documentation index, see [llms.txt](https://docs.eclipsepad.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eclipsepad.com/tokenomics/deflationary-model.md).

# Deflationary Model

At Eclipse Pad we understand the value of ecosystem value capture along both a short and long-term view. short-term, not just long-term ecosystem value capture which is the reason for building the [Rewards Pool](/eclipse-mechanics/rewards-pool.md), but the shorter-term value capture is also important. This is why we have implemented a deflationary token model on Eclipse Pad.

### Buyback and Burn

A portion of the fees collected across the platform will automatically go towards $ECLIP token buybacks. A portion of these tokens will then be burnt, taking them out of circulation permanently. The rest will go towards boosting the token distributions for staking.


---

# 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.eclipsepad.com/tokenomics/deflationary-model.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.