> For the complete documentation index, see [llms.txt](https://docs.reserve.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reserve.org/core-components/index-dtfs.md). # Index DTFs Index DTFs let you own a share of everything. They do this by holding diversified baskets of tokenized assets within a single onchain product. Below is a detailed overview of how Index DTFs function within the Reserve ecosystem. *** ## TL;DR **Index DTFs are like ETFs, but decentralized: they’re permissionless, composable, and live 24/7 onchain.** Index DTFs package up to 100+ onchain assets into single ERC‑20 tokens, bringing index investing onchain with a new degree of openness, accessibility, and efficiency. ## Key features Index DTFs deliver broad exposure, transparent execution, and flexible governance through a lightweight, fully onchain architecture. * **Diversified exposure**: Package 10+ assets on Ethereum and 100+ on Base * **Broad asset support**: Use virtually any ERC-20; no oracles or plugins needed * **Permissionless access**: Anyone can mint, redeem, or deploy * **Flexible onchain governance**: Use any token for custom decentralized governance * **Automatic liquidity engine**: Tap deep onchain liquidity for smooth rebalancing and low tracking error --- # 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.reserve.org/core-components/index-dtfs.md?ask=&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.