> For the complete documentation index, see [llms.txt](https://hello-fun-1.gitbook.io/hello.fun-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hello-fun-1.gitbook.io/hello.fun-docs/introduction/how-hello.fun-works.md).

# How Hello.Fun Works

Hello.Fun takes a token from creation to an open liquidity market through one connected launch process.

A launch begins with an idea, token creation and immediate bonding curve trading. Creators can use HELLO Pilot to help shape and prepare their launch before moving through the standard Hello.Fun launch flow.

As trading progresses, the launch can reach its graduation requirement. At graduation, the market transitions into Uniswap v4 and liquidity is permanently locked.

### The Hello.Fun Flow

```mermaid
flowchart LR
    A["Idea"] --> B["Create Token"]
    B --> C["Launch"]
    C --> D["Bonding Curve Trading"]
    D --> E["Graduation"]
    E --> F["Uniswap v4 Pool"]
    F --> G["Permanent Liquidity"]
    G --> H["Open Market Trading"]
```

### 1. Create Your Token

The creator connects a wallet and begins building the token.

HELLO Pilot adds AI assistance to this stage of the experience, helping creators move from an idea toward a more structured launch.

The creator enters the token details, including:

* Token name
* Token symbol
* Description
* Token image
* Optional website
* Optional X profile
* Optional Telegram community
* Creator fee

The creator then reviews the launch and signs the transaction from their wallet.

Each Hello.Fun token has a fixed total supply of **1,000,000,000 tokens** with **18 decimals**.

The entire supply is created once when the token launches. There is no function that allows additional tokens to be minted later.

### 2. Launch the Market

The token and its bonding curve are created as part of the launch.

The complete token supply is moved into the bonding curve and trading becomes available immediately.

There is no separate process required to activate trading after the token has been created.

### 3. Trade on the Bonding Curve

Before graduation, buying and selling takes place through the token's bonding curve.

Buyers provide the pairing asset and receive tokens from the curve.

Sellers can return tokens to the curve in exchange for the pairing asset.

As tokens are purchased from the curve, the market progresses toward graduation.

### 4. Reach Graduation

Graduation is the transition between the initial bonding curve market and the token's Uniswap v4 market.

Once the required conditions are reached, the launch becomes ready to graduate.

The reserves accumulated through bonding curve trading are then used to create the graduated market.

If the automatic graduation process does not complete successfully, graduation can still be completed through the protocol.

### 5. Move to Uniswap v4

At graduation, the launch transitions from the bonding curve into a Uniswap v4 liquidity pool.

The accumulated reserves are used to seed the pool, with its opening market state derived from the final state of the bonding curve.

From this point, trading continues through the graduated liquidity market rather than the bonding curve.

### 6. Lock the Liquidity

The liquidity position created during graduation is transferred into the Hello.Fun liquidity locker.

The liquidity principal is permanently held by the locker.

There is no function for withdrawing, unlocking, transferring or removing that liquidity principal from the locker.

This means the graduated liquidity position does not depend on the creator choosing to keep the liquidity in place.

### 7. Continue Trading

Graduation does not end the token's market.

It changes how that market operates.

```mermaid
flowchart TD
    A["Before Graduation"] --> B["Bonding Curve"]
    B --> C["Graduation"]
    C --> D["After Graduation"]
    D --> E["Uniswap v4"]
    E --> F["Continued Trading"]
```

Before graduation, trades use the bonding curve.

After graduation, trades use the Uniswap v4 market.

Hello.Fun handles this progression as part of the launch lifecycle.

### One Continuous Market Journey

Hello.Fun connects the stages that normally sit separately across a token launch.

**Idea → Create → Launch → Trade → Graduate → Lock Liquidity → Continue Trading**

HELLO Pilot adds intelligence to the beginning of that journey, while the Hello.Fun protocol provides the market infrastructure that carries the token from launch into open market trading.

The result is a defined path from an idea to a live token and an open liquidity market, while users continue to control and sign their own transactions throughout the process.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hello-fun-1.gitbook.io/hello.fun-docs/introduction/how-hello.fun-works.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
