# Earn Token Listing

Blueberry DAO is very careful about adding new collateral assets as this is a common cause of exploits. However, the protocol is able to support more exotic collaterals safely because it can isolate possible deployments and usages of the assets. 

In general, Blueberry DAO only supports highly liquid collateral assets to be borrowed against in amounts that can be liquidity against locked or verified external liquidity sources. This is a very case-by-case situation. 

Regardless of the asset, the DAO will first perform a thorough review with its security partners to account for any risks and the value add to the system. As a general rule of thumb, Blueberry can support longer tail assets in lending markets and be utilized for deployments, but not as a collateral option.

**Listing Standards as evaluated by DAO contributors:**

* All tokens should adhere to a maximum of 18 decimals places and tokens that can not be directly upgraded.
* Sufficient Locked/burned liquidity on-chain 
  * This is having liquidity locked into a trading venue to make sure trades can always occur that are locked either through a contract or through code. 
* Team
  * Who created the project
* Backers
  * Who is supporting the project 
* Treasury and Assets supporting the project 
* Trading activity
  * That this token isn't fully dormant and has no volume
* Oracle support
  * This should be supported by Chainlink price feeds.
* Isn't a newly launched token 

These are the beginning process to see if a token can be whitelisted in the protocol and see the level of utilization that it can get. 

<br>


---

# Agent Instructions: 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:

```
GET https://v1.docs.blueberry.garden/earn/earn-token-listing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.