> For the complete documentation index, see [llms.txt](https://docs.behodler.io/user-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.behodler.io/user-docs/ecosystem/behodler/new-tokens-listings-on-behodler.md).

# New tokens listings on Behodler

All new tokens added to Behodler will go through a pre-seeding process via the Limbo Dapp.

Via the upcoming Limbo release, at least 100 new tokens will be added and go through the pre-seeding process, incentivized with the Flan rewards token.

Curation of this list of new token additions is ongoing, and subject to security review. For now, tokens to be listed will meet a certain standard such as no unilateral admin minting function and overflow/underflow checks such as OpenZeppelin.

Here is a sample of likely additions, subject to change:

Aave, COMP, CRV, 0x, 1inch, Badger, BAL, REN, Rune, Sushi, Uni.

We also plan to list a diverse amount of popular LP tokens and interest bearing tokens, so liquidity providers and holders of yield tokens can easily and inexpensively swap positions

For example:

aSUSD, Uniswap v2 DAI/USDC LP, Uniswap v2 USDC/ETH LP, Sushiswap DAI/USDC LP, curve stETH/ETH LP, xSushi, kETH.

An ongoing proposed list can be found [here](https://docs.google.com/spreadsheets/d/19AE_4aHMb9EVTBtZNG3p5oj69G1lX7j89VDzbPGOIGw/edit#gid=0).


---

# 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.behodler.io/user-docs/ecosystem/behodler/new-tokens-listings-on-behodler.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.