> For the complete documentation index, see [llms.txt](https://oboswap.gitbook.io/oboswap/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oboswap.gitbook.io/oboswap/obos/controlling-obo-supply.md).

# Controlling OBO supply

![](/files/JVU7MBPaT0Bo8ws62fEm)

## Why OBOS has no hard cap

There's currently no hard cap on the supply of OBOS token, making it an inflationary token.

Community members often point to this as a cause for concern, and while the chefs certainly understand the wish for a hard cap, there's a big reason we don't expect to set one in the near future:

> OBO's primary function is to incentivize providing liquidity to the exchange. *Without block rewards, there would be much less incentive to provide liquidity (LP fees etc. would remain).*

**So what are the other ways OBOS supply is limited, to counter inflation?**

## How OBOS supply is reduced without a hard cap

The chefs aim to **make deflation higher than emission** by building deflationary mechanisms into Obo swap's products**.** The goal is for more OBOS to leave circulation than the amount of OBOS that's produced.

### Deflationary mechanisms

Regular token burns are built into many of Obo Swap's products with more on the way. Check the **OBOS Tokenomics page** for details on present and upcoming deflationary mechanisms..


---

# 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://oboswap.gitbook.io/oboswap/obos/controlling-obo-supply.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.