> For the complete documentation index, see [llms.txt](https://docs.liqd.ag/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liqd.ag/liquidlaunch-integration/creating-tokens.md).

# Creating Tokens

Call `createToken` on the LiquidLaunch contract (HyperEVM) to deploy a new token with bonding curve trading.

**Contract:** `0xDEC3540f5BA6f2aa3764583A9c29501FeB020030`

```solidity
function createToken(
    string memory name,
    string memory symbol,
    string memory image_uri,
    string memory description,
    string memory website,
    string memory twitter,
    string memory telegram,
    string memory discord,
    uint8 dexIndex
) external payable returns (address tokenAddress)
```

## Parameters

| Parameter     | Required | Description                           |
| ------------- | -------- | ------------------------------------- |
| `name`        | yes      | Token name (e.g. "Awesome Coin")      |
| `symbol`      | yes      | Trading symbol (e.g. "AWE")           |
| `image_uri`   | yes      | URL for token logo (IPFS recommended) |
| `description` | yes      | Brief description of the token        |
| `website`     | no       | Project website URL                   |
| `twitter`     | no       | Twitter handle or URL                 |
| `telegram`    | no       | Telegram group/channel link           |
| `discord`     | no       | Discord server link                   |
| `dexIndex`    | yes      | Reserved — use `0`                    |

## Initial buy protection

Any HYPE sent with the `createToken` transaction automatically purchases tokens for the creator before anyone else can buy. This prevents front-running / sniping.

## Creator restrictions

* **1-hour sell lock** — creators cannot sell their tokens for 1 hour after creation


---

# 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://docs.liqd.ag/liquidlaunch-integration/creating-tokens.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.