> 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/introduction/how-to-participate.md). # How to participate ### Users Hold, earn, and transact in asset-backed value through DTFs and consumer products built on the Reserve ecosystem, including UGLYCASH. ### Investors Gain diversified exposure to tokenized assets through Index DTFs, and earn yield through Yield DTFs as the ecosystem grows. ### RSR holders Own a share in the value of everything by participating in governance, staking, and value accrual mechanisms tied to DTF adoption. ### Builders Create new DTFs, financial products, and applications on top of Reserve using open, permissionless infrastructure. ### Partners Distribute Reserve-powered products, integrate asset-backed value into existing platforms, or extend access through new channels. ### Contributors Support protocol development, ecosystem growth, education, and alignment through core contributor organizations and initiatives. --- # 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/introduction/how-to-participate.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.