# Blackhole

## What Is It?

A black hole is an address that can receive tokens but has no function to send them out. Tokens sent there are permanently locked — they can never be retrieved by anyone.

In Crypto DAO, all LP tokens created through bonding are sent to a black hole address.

## How It Works

```
User bonds USDT
    ↓
Contract creates LP (USDT + PRO)
    ↓
LP sent to black hole address
    ↓
LP is locked forever
    ↓
Liquidity permanently available for trading
```

## Properties

| Property           | Meaning                                          |
| ------------------ | ------------------------------------------------ |
| **No withdrawal**  | No function exists to remove tokens              |
| **No private key** | Either no key exists, or it's provably destroyed |
| **Irreversible**   | Cannot be changed, even by team                  |
| **Verifiable**     | Anyone can check the address on-chain            |

## Why This Matters

### Guaranteed Liquidity Floor

Normal LP:

```
LP providers can withdraw anytime
    → During panic, they withdraw
    → Liquidity disappears
    → Token becomes illiquid
    → Price crashes further
```

Black hole LP:

```
LP is locked permanently
    → During panic, LP stays
    → Liquidity remains
    → Trading continues
    → Price has floor
```

### Rug Pull Prevention

With normal LP, teams can:

* Remove liquidity
* Drain trading pool
* Leave users with worthless tokens

With black hole LP:

* No removal function exists
* Even team cannot drain
* Liquidity is permanent

## Verification

{% stepper %}
{% step %}

### Get the address

Listed in [Contracts & Addresses](broken://pages/6372f0d91c381c29b890fe5f927f0c88387f5b0d)
{% endstep %}

{% step %}

### Check balance

View LP token balance on explorer
{% endstep %}

{% step %}

### Review contract

Confirm no withdrawal functions
{% endstep %}

{% step %}

### Check history

Only inflows, never outflows
{% endstep %}
{% endstepper %}

## Cumulative Effect

Every bond adds permanent liquidity:

| Time    | Bonds  | LP Locked | Effect            |
| ------- | ------ | --------- | ----------------- |
| Month 1 | 100    | 100 LP    | Base liquidity    |
| Month 6 | 1,000  | 1,000 LP  | Deeper liquidity  |
| Year 1  | 5,000  | 5,000 LP  | Substantial floor |
| Year 2  | 15,000 | 15,000 LP | Robust trading    |

The longer the protocol runs, the stronger the liquidity foundation.

## Common Questions

<details>

<summary>Can the team access black hole funds?</summary>

No. No private key exists. No withdrawal function exists.

</details>

<details>

<summary>What if there's a bug?</summary>

The contract is audited to have no extraction path. No function = no exploit vector for withdrawal.

</details>

<details>

<summary>Can governance unlock it?</summary>

No. Governance can only call functions that exist. No unlock function exists.

</details>

<details>

<summary>What about protocol upgrades?</summary>

The black hole address is immutable. New contracts cannot access old black hole funds.

</details>

## Trade-off

Black hole liquidity is a one-way commitment:

| Benefit             | Cost                            |
| ------------------- | ------------------------------- |
| Permanent liquidity | Cannot be reallocated           |
| Rug pull impossible | Cannot respond to all scenarios |
| Trust minimized     | Flexibility reduced             |

The protocol chose certainty over flexibility.

## Related

* [Protocol-Owned Liquidity](broken://pages/22d2713dbfeee92faf82db77ed88aaf0f5090da6)
* [How Bonds Work](broken://pages/5ccd29569b0bc71b9a2ddd765a3f167b4cacfddc)
* [RBS System](broken://pages/aa76b2e1428c9d09a9886d2a6271582fc2f8d565)


---

# 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://cryptodao-it.gitbook.io/c-dao/2.-mechanics/price-stability/blackhole.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.