# Long-tail and exotic asset support

Traditional money markets such as Aave and Compound make it hard for long-tail and exotic assets to get listed on their platforms due to extensive liquidity thresholds in order to shield the protocol TVL since all the assets are grouped in a single pool, thus exposing the risk of a single asset to the entire TVL in the protocol.

Therefore, many protocols are unable to add their tokens as collateral in money markets.

On the other hand, Ionic uses the isolated pool model, which enables a wider range of collateral since each asset is only exposed to the risk of the individual pool instead of the broader protocol.

The customizable nature of the platform allows for the creation of separate lending markets for different groups of assets on various EVM chains and allows pool creators to customize a wide range of parameters.

Additionally, Ionic takes a consultative approach in pool design and partners with pool creators to help raise awareness to consider key parameters (ie. liquidity depth, supply caps, loan-to-value, etc.) to help ensure the safety of these custom pools.

This allows exotic and long-tail assets to participate in DeFi lending, which allows protocol partners, treasury and other trusted allies to access the liquidity of these long-tail assets without the need to sell them, thus enabling a wide range of strategies and use cases based on how pool creators structure these pools.


---

# 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://docs.ionic.money/partner-and-pool-operator-documents/ionic-for-partners/long-tail-and-exotic-asset-support.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.
