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

# Controlling $HOPE supply

## Does HOPE have a hard cap?

Yes, HOPE now has a hard cap of 750M&#x20;

## How HOPE supply is reduced

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

### Reducing block emissions

By reducing the amount of HOPE made per block, we slow inflation. This has already been done once: Since the first reduction in block emissions, we've already effectively reduced the number of HOPE entering circulation from 40 HOPE per block to 13.75. But we don't want to do this too frequently, too early, we want to still incentivize people to provide liquidity.

### Deflationary mechanisms

Regular token burns (view burn address) are built into many of HopiumSwap's products (like a 10% burn of HOPE spent on lottery tickets), with more on the way. Check the [**HOPE Tokenomics page**](https://docs.hopiumswap.info/product-docs/tokenomics/hope/cake-tokenomics) 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:

```
GET https://funpump.gitbook.io/funpump/tokenomics/usdhope/controlling-cake-supply.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
