> For the complete documentation index, see [llms.txt](https://cryptify.gitbook.io/cryptify/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cryptify.gitbook.io/cryptify/revenue-and-payment-structure/usdcrypt-buyback-and-burn-program.md).

# $CRYPT Buyback & Burn Program

Unlike many projects that rely solely on hype, Cryptify prioritizes long-term value for our native token, $CRYPT. We achieve this through a buyback and burn program, strategically designed to foster a thriving $CRYPT ecosystem.

### **Buyback and Burn Explained:**

This strategy reduces the total supply of $CRYPT tokens, potentially increasing their value. Here's how it works:

* **Continuous Buybacks:**
  * **50% of platform profits** are consistently used to repurchase $CRYPT from circulation.
  * After 3 months, an **additional 20% of all platform taxes** are also allocated for further buybacks.
* **Deflationary tokenomics:**
  * Repurchased $CRYPT tokens are permanently burned, reducing overall supply.
  * Fewer tokens, potentially higher value per token.

### **Why Buyback and Burn?**

By strategically reducing supply, the program can positively influence price:

* **Scarcity:** Fewer tokens = potentially more valuable tokens.
* **Holding Incentive:** Potential price appreciation encourages holding $CRYPT, promoting a healthy token ecosystem.


---

# 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://cryptify.gitbook.io/cryptify/revenue-and-payment-structure/usdcrypt-buyback-and-burn-program.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.