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

# Buyback and burn

10% of the yield to the team, 90% buys PSTR on the market and burns it.

The buyback contract receives the yield, converted to HYPE.

| Share of the yield | Goes to                                   |
| ------------------ | ----------------------------------------- |
| 10%                | The team wallet                           |
| 90%                | Buying PSTR on HyperSwap, then burning it |

## How a buyback runs

* Buybacks are public: anyone can trigger one; the keeper does. Each one is bounded (per call, per interval, and at most 2% of the pool's HYPE reserve), so the yield is spent in a stream, not in one spike.
* Every PSTR received is burned in the same transaction.

## The buyback pays the tax too

A buyback is a buy like any other: 10% of it is tax, which goes to the treasury. Part of every buyback therefore becomes more PAPER, and the loop closes.

## What you can check

HYPE received, spent on buybacks and PSTR burned are all on-chain counters. See [Verify the numbers](/transparency/verify.md).


---

# 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.paperstrategy.xyz/the-loop/buyback.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.