> For the complete documentation index, see [llms.txt](https://sacred.gitbook.io/sacred-finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sacred.gitbook.io/sacred-finance/tokenomics-1/sacred-buy-backs.md).

# Sacred Buy Backs

The process outlined below will start at the end of the 3rd month after Sacred Finance’s IDO. From the start of this date.

1. At the end of each month, the DAO shall: 
   * Calculate the total revenue gained by Sacred over that month.
     *  If the revenue is under $1000, there will be no buybacks and the revenue will be placed into the treasury. 
   * 10% of that revenue to buying back SACRED from the open market. 
2. This portion shall be used to buy SACRED on any DEX, ensuring that it is purchased at a reasonable rate to keep the slippage at or below 3%.
3. The purchased SACRED shall be transferred to the treasury. 
4. A record of these transactions shall be maintained for auditing purposes.


---

# 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://sacred.gitbook.io/sacred-finance/tokenomics-1/sacred-buy-backs.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.