> For the complete documentation index, see [llms.txt](https://dopot.gitbook.io/dopot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dopot.gitbook.io/dopot/dopot-ecosystem/crowdfunding.md). # Crowdfunding ### Basics Each project is composed of one or more reward tiers, investing in one will grant the user a semi-fungible token representing the right to receive the corresponding product(s). The token is fungible, by being redeemable for the initial investment until the project reaches its pre-set funding goal. Then it becomes non-fungible — a proof of participation in the project, and its value is completely up to the market. ### Security Project creators and investors are protected in many ways, and with the aid of a decentralized arbitration protocol and the Dopot DAO, no middlemen are required. Additionally, a small percentage of each crowdfunding campaign is transferred to a shared insurance-like vault; if any issue with the reward delivery arises users can open arbitrations cases and eventually receive a refund. Please note: full funds recovery might not be possible when funds in the vault are insufficient. --- # 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://dopot.gitbook.io/dopot/dopot-ecosystem/crowdfunding.md?ask=&goal= ``` `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.