# The Black Hole

**TwiceProtocol** is meant to be a **lasting Protocol**, even though it is largely made of pretty **Degen/High APR products** that would usually tear projects apart in a couple weeks. \
To achieve such a feat, we needed to implement **a few deflationary mechanisms** that will help **sustain the protocol** by **burning $TWICE tokens** to **reduce the supply** and **reinforce token value**.

A percentage of **every buy, sell and create transaction** on **TwiceProtocol** goes to the **Black Hole** **wallet**. 75% of this wallet is then **burned** by being sent to the **Void** (aka a 0x0000 address). The remaining 25% tokens are **redistributed back to $TWICE holders via our Wormhole** in the shape of our **Squared Rank** and **Referral systems**.

**Here's how it goes:**

<figure><img src="/files/emZvZSAUzAJale9dKTq6" alt=""><figcaption></figcaption></figure>

*<mark style="color:red;">**KEEP IN MIND THAT RANDOMLY TRIGGERED ON-CHAIN EVENTS WILL POSSIBLY ALTER THESE SETS OF RULES AND VALUES AND REMEMBER TO DESIGN YOUR STRATEGY ACCORDINGLY.**</mark>*


---

# Agent Instructions: 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://twiceprotocol.gitbook.io/twiceprotocol/tokenomics/the-black-hole.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.