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

# Trading

Buy and sell tokens on the LiquidLaunch bonding curve. All functions are on the LiquidLaunch contract (`0xDEC3540f5BA6f2aa3764583A9c29501FeB020030`).

## Buying tokens

```solidity
function buyTokens(address token) external payable
```

Send HYPE as `msg.value`. The contract calculates tokens based on the bonding curve, deducts the 1% fee, and transfers tokens to your wallet.

## Selling tokens

```solidity
function sellTokens(address token, uint256 tokenAmount) external
```

Specify how many tokens to sell. You receive HYPE minus the 1% fee. No approval required.

## Estimating trades

Always estimate before trading to understand price impact:

```solidity
function estimateBuy(address token, uint256 hypeAmount) public view returns (uint256)
function estimateSell(address token, uint256 tokenAmount) public view returns (uint256)
```

Both estimates include the 1% fee deduction.

## Checking reserves

```solidity
function getLiquidity(address token) public view returns (uint256 hypeReserve, uint256 tokenReserve)
```

Returns current virtual reserves. Useful for understanding price impact before large trades.

## Full contract reference

All functions, events, data structures, and error codes are documented in the [Contract Reference](/liquidlaunch-integration/api-reference.md).


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.liqd.ag/liquidlaunch-integration/trading.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 `build a script that syncs our docs to a CMS` 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.