> For the complete documentation index, see [llms.txt](https://docs.taxsplit.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.taxsplit.app/documentation/taxsplit/liquidity-management.md).

# Liquidity Management

### Liquidity management

Adding liquidity is crucial for your token’s success.

* Enables trading on decentralized exchanges
* Helps provide price stability

TaxSplit supports both **Raydium** and **Meteora**.

#### Adding liquidity

{% stepper %}
{% step %}

### Choose your DEX

Select between:

* **Raydium** (most popular)
* **Meteora** (lower fees)

Each has different fee structures and pool types.
{% endstep %}

{% step %}

### Set initial price

Determine your token’s starting price by setting the SOL/token ratio.

This is critical for your tokenomics.
{% endstep %}

{% step %}

### Add liquidity

Deposit equal values of SOL and your token.

More liquidity generally means less price slippage for traders.
{% endstep %}
{% endstepper %}

#### Locking LP tokens

Locking LP tokens proves to your community that you won’t remove liquidity (rug pull). This builds trust.

* **Lock duration**: choose from **1 month** to **5 years** (longer locks build more trust)
* **Verification badge**: locked liquidity earns a **blue verification badge** on TaxSplit


---

# 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://docs.taxsplit.app/documentation/taxsplit/liquidity-management.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.