> For the complete documentation index, see [llms.txt](https://wp.gotmlabz.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wp.gotmlabz.io/nebula/bonding-curve.md).

# Bonding Curve

When the token reaches a predefined market cap (e.g., $69,000 on Solana), the protocol automatically adds liquidity to Raydium and burns a portion of the tokens. This creates a guaranteed level of liquidity, allowing for trading on Raydium

When a coin is launched on Pump.fun, 800 million tokens are put into the bonding curve.

All coins generated are identical, with a total of one billion tokens.

Sales and Bonding Curve Fulfillment:

The objective after the coin launch is to promote and sell 800 million tokens.

Once all 800 million tokens are sold, the bonding curve reaches full capacity and automatically transitions to Radium.

SOL Requirement for Radium Access:

The approximate number of SOLs required to transition to Radium is 86.

This number fluctuates slightly, typically between 84 and 86 SOL.

Market Cap Thresholds:

Approximately 45 SOL is needed to reach the “King of the Hill” status, representing a halfway point in terms of token sales


---

# 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://wp.gotmlabz.io/nebula/bonding-curve.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.