> For the complete documentation index, see [llms.txt](https://rcofinance.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rcofinance.gitbook.io/whitepaper/market-challenges/vii.-no-diverse-assets.md).

# VII. No Diverse Assets

Retail investors often struggle to access diverse asset classes like exchange-traded funds (ETFs), stocks, and derivatives due to high liquidity requirements and significant entry costs. For example, a study by the Investment Company Institute found that the average expense ratio for ETFs was 0.44% in 2021, which can add up over time and reduce returns for retail investors with smaller portfolios.

Liquidity in ETFs is also complex, depending on both the liquidity of the underlying assets and the trading volume of ETF shares, which can lead to higher costs and reduced access for retail investors when disruptions occur. Additionally, high minimum investment thresholds and the complexity of some financial products discourage many from participating, limiting their ability to effectively diversify their portfolios.


---

# 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://rcofinance.gitbook.io/whitepaper/market-challenges/vii.-no-diverse-assets.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.
