> 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/usdhello.md).

# $HELLO

$HELLO is the planned ecosystem token of Hello.Fun.

It is designed to become part of the platform's broader pairing and economic ecosystem as Hello.Fun expands beyond its initial ETH market.

The current Hello.Fun platform operates with ETH as its live pairing asset. $HELLO functionality represents a future stage of the Hello.Fun ecosystem.

### The Role of $HELLO

The Hello.Fun vision gives $HELLO a role beyond simply existing alongside the platform.

It is designed to become part of how tokens launch, how markets connect and how value circulates through the broader Hello.Fun ecosystem.

```mermaid
flowchart TD
    A["Hello.Fun"] --> B["Token Launches"]
    A --> C["Pair Markets"]
    A --> D["Platform Activity"]
    A --> E["$HELLO Ecosystem"]
    E --> F["$HELLO Pairing"]
    E --> G["Creator Incentives"]
    E --> H["Hello Economy"]
```

### $HELLO as a Pairing Asset

A central planned utility for $HELLO is its use as a pairing asset.

Instead of every token beginning with the same market, creators will be able to choose from supported pairing assets as the Hello.Fun ecosystem expands.

$HELLO is intended to become one of those choices.

```mermaid
flowchart LR
    A["Create Token"] --> B["Choose Supported Pair"]
    B --> C["$HELLO"]
    C --> D["Launch Market"]
```

A $HELLO paired launch would use $HELLO as the asset on the other side of the token's market.

This makes $HELLO part of the market structure itself.

### Pairing Creates Utility

Pairing gives an ecosystem token a functional role inside new markets.

When a token launches against $HELLO, activity around that launch can also create activity around $HELLO as its pairing asset.

```mermaid
flowchart LR
    A["New Token"] --> B["Paired With $HELLO"]
    B --> C["New Pair Market"]
    C --> D["Trading Activity"]
    D --> E["$HELLO Ecosystem Activity"]
```

This is part of the broader Hello.Fun idea:

**The pair is part of the idea.**

### Creator Incentives

Hello.Fun also plans additional creator incentives around $HELLO paired launches.

The ecosystem design includes **Enhanced Creator Rewards** for creators who choose $HELLO as their pairing asset.

These incentives are intended to make $HELLO pairing a meaningful choice within the launch experience rather than simply another available market.

The exact implementation of these benefits will form part of the $HELLO ecosystem rollout.

### The Hello Economy

$HELLO is also designed to connect with the broader economic model planned for Hello.Fun.

The Hello Economy is intended to connect:

1. Platform activity
2. $HELLO
3. Hello.Fun launches
4. Market buybacks
5. Ecosystem growth

```mermaid
flowchart TD
    A["Hello.Fun Activity"] --> B["Hello Economy"]
    B --> C["$HELLO"]
    B --> D["Hello.Fun Launches"]
    C --> E["Ecosystem Growth"]
    D --> E
```

The following pages explain this model in greater detail.

### Fixed Supply Vision

The planned total supply for $HELLO is:

**1,000,000,000 $HELLO**

The proposed ecosystem allocation is:

| Allocation                    |    Share |            Tokens |
| ----------------------------- | -------: | ----------------: |
| Liquidity                     |      45% |       450,000,000 |
| Creator and Ecosystem Rewards |      25% |       250,000,000 |
| Community and Growth          |      15% |       150,000,000 |
| Treasury                      |      10% |       100,000,000 |
| Team                          |       5% |        50,000,000 |
| **Total**                     | **100%** | **1,000,000,000** |

These tokenomics describe the planned $HELLO ecosystem structure.

### Current Platform and Future Ecosystem

It is important to distinguish the current Hello.Fun launch system from the planned $HELLO ecosystem.

#### Available Today

Hello.Fun currently supports:

1. Token creation
2. ETH pairing
3. Bonding curve trading
4. Graduation
5. Uniswap v4 markets
6. Permanent liquidity locking
7. Creator fees
8. Market discovery and trading

#### Planned With $HELLO

The broader ecosystem is designed to introduce:

1. $HELLO as a pairing asset
2. Enhanced Creator Rewards for $HELLO paired launches
3. $HELLO centered ecosystem incentives
4. The broader Hello Economy

```mermaid
flowchart LR
    A["Hello.Fun Today"] --> B["ETH Launch Markets"]
    B --> C["Ecosystem Expansion"]
    C --> D["$HELLO"]
    D --> E["$HELLO Pair Markets"]
    D --> F["Hello Economy"]
```

### Built Around the Pair

$HELLO is designed to become part of what makes Hello.Fun different.

Not simply a token beside the launchpad.

A token that can become part of the markets created through it.

**Pick your pair. Pick your market. Say HELLO to what’s next.**


---

# 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/usdhello.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.
