> For the complete documentation index, see [llms.txt](https://bread-5.gitbook.io/bread/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bread-5.gitbook.io/bread/mechanics/graduation-and-migration.md).

# Graduation and migration to Meteora

### When graduation triggers

Graduation triggers when the bonding curve collects **45 SOL** of real liquidity.

At that moment:

1. Further buys on the curve are blocked
2. The smart contract starts migration

### What happens at migration

**Bonding Curve → Meteora:**

The 45 SOL collected splits into three pools:

* **80% (\~36 SOL)** → Meteora DAMM liquidity
* **15% (\~6.75 SOL)** → buyback and burn of the same token (executed as 5 tranches × 20% every 5 minutes, total 25 minutes)
* **5% (\~2.25 SOL)** → migration fee

**Presale → Meteora:**

The 45 SOL collected splits into three pools — same distribution as in Bonding Curve:

* **80% (\~36 SOL)** → Meteora DAMM liquidity
* **15% (\~6.75 SOL)** → buyback and burn of the same token (5 tranches × 20% every 5 minutes)
* **5% (\~2.25 SOL)** → migration fee

### Creating the Meteora pool

The contract creates a Meteora DAMM pool with a TOKEN/SOL pair. The pool receives:

* 80% of SOL liquidity
* 200M tokens from the migration reserve

### LP token lock

The pool's LP tokens are locked **permanently**. Nobody can pull liquidity from the pool.

* The creator cannot rug-pull by withdrawing LP
* Liquidity stays in the pool forever
* Holders are protected from classic rug schemes

### Lifting the limits

* Max Buy is lifted
* Sell tax no longer applies
* Trading runs on Meteora like a regular SPL token

### What changes for holders after migration

* You can sell without the 15% sell tax
* Slippage becomes larger — typical for any DAMM pool
* Price is determined by the market, not the bonding curve
* All standard DeFi options open up — Jupiter routing, limit orders, etc.

***


---

# 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://bread-5.gitbook.io/bread/mechanics/graduation-and-migration.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.