> For the complete documentation index, see [llms.txt](https://goattrading.gitbook.io/dojo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://goattrading.gitbook.io/dojo/features/liquidity-pools.md).

# Liquidity Pools

When creating a token, 100% of the supply is deposited into a Sushi V3 liquidity pool. The price it starts at is a $15k market cap to discourage cheap initial sniping that’s much easier with smaller starting market caps. All liquidity in this pool is immediately burnt so it can never be withdrawn.

Because pools are launched using Sushi V3, tokens are also able to traded on the Sushi website without any interaction with Dojo. This is only available for Classic tokens to start because of router additions needed for tax tokens, but tax tokens have this capability added soon. This allows teams to simply launch a token and pool on Dojo but tell users to trade on Sushi if they want to take their own path rather than continue trading on Dojo.

Liquidity pools do not have a certain market cap where they migrate anywhere. Tokens are launched on Sushi V3, stay on Sushi V3, and Goat, Sushi, and the creator profits from fees generated there forever. This ensures fees are generated even when a token is very large and should reduce the number of problems that spring up when a token migrates to other protocols.


---

# 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://goattrading.gitbook.io/dojo/features/liquidity-pools.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.